[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-323?pag...
]
Oliver Siegmar commented on HSEARCH-323:
----------------------------------------
I agree that the dummy directory is a dirty hack but the way HSEARCH-532 solve this issue
doesn't help me. In our environment the application that provides the master
repository is deployed in the same appserver and is (could be) started after the
client-apps. Because the appserver starts the applications in sequence (an not in
parallel), the implementation of HSEARCH-532 would just do some retries and cause longer
startup period.
Fault tolerant FSSlaveDirectoryProvider
---------------------------------------
Key: HSEARCH-323
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-323
Project: Hibernate Search
Issue Type: Improvement
Components: directory provider
Affects Versions: 3.1.0.GA
Reporter: Oliver Siegmar
Attachments: FSSlaveDirectoryProvider.java.diff
The current implementation of FSSlaveDirectoryProvider requires an existent master
repository at startup. In our environment it could happen, that the master repository is
built some time after the clients (using the FSSlaveDirectoryProvider) are being started.
It'd be good to have a more fault tolerant FSSlaveDirectoryProvider, that would retry
to initialize itself (using a TimerTask for example). The configuration should allow to
enable/disable this feature and to specify the retry interval and period.
--
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