[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-532?pag...
]
Emmanuel Bernard commented on HSEARCH-532:
------------------------------------------
I wonder if it's the right thing to do actually.
We know the system won't boot properly today if the master is not started first and
initialize the directory structure. Adding a retry n times would only be here to hide the
fundamental weakness. Or is there a use case I am missing?
FSSlaveDirectoryProvider could retry several times when the current
marker file is not found
--------------------------------------------------------------------------------------------
Key: HSEARCH-532
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-532
Project: Hibernate Search
Issue Type: Bug
Components: directory provider
Affects Versions: 3.1.1.GA, 3.2.0.Beta1, 3.2.0.CR1, 3.2.0.Final
Reporter: Hardy Ferentschik
Fix For: 3.3.0
The {{FSMasterDirectoryProvider}} has a hole in the startup procedure where it is
possible for the {{FSSlaveDirectoryProvider}} to not being able to find the current marker
file. At the moment the startup for the slave will fail in this case. We could let the
{{FSSlaveDirectoryProvider}} retry for a couple of times to allow the master to create the
marker file.
This problem can also occur during runtime, but there the {{FSSlaveDirectoryProvider}}
just skips a sync. However, we log this as error. Probably should just be a warning.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira