[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-614?pag...
]
Hardy Ferentschik commented on HSEARCH-614:
-------------------------------------------
Since I haven't seen this mentioned - the problem only occurs on {{start()}}. If this
situation occurs after the directory is started the error is logged and the slave index
directory does not get switched - skipping one synchronization. On {{start()}} the
assumption is that the slave has to be able to successfully get an initial copy of the
index. Depending on when master and slave are getting started this could even happen with
"reasonable" refresh properties.
One solution would be to add some retry operation for {{start()}}. is it worth it? Maybe
it is better to fail early. In a proper application setup you would (hopefully) have some
sort of monitoring/startup harness around your apps.
FileNotFoundException during slave synchronization with source
--------------------------------------------------------------
Key: HSEARCH-614
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-614
Project: Hibernate Search
Issue Type: Bug
Components: directory provider
Affects Versions: 3.1.0.GA, 3.1.1.GA, 3.2.0.Final, 3.2.1, 3.3.0.Beta2
Environment: Hibernate 3.6, Oracle 10g
Reporter: Michael Mogley
Priority: Minor
Fix For: 3.3.0.CR1
The current file synchronization mechanism in the FSSlaveDirectoryProvider has the
potential to throw a FileNotFoundException if the source file it's copying is deleted
before the copy operation completes.
https://forum.hibernate.org/viewtopic.php?f=9&t=1007801&p=2437680...
--
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