New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recovery: RecoveryTarget does not fsync the right file name #9144
Comments
I fixed this in Lucene 5 and trunk through LUCENE-6150. |
Ah you mentioned this already! |
Yes, I found about it while upgrading to a more recent Lucene 5 snapshot :) This is much less trappy now! |
grrrr....!!! |
For the record, this bug was introduced in #8092 which is only on master and 1.x so the bug has not been released. |
Hehe, it was useful to fix the staleFiles mess! Thanks for confirmation. I had exectly this problem in mind when looking into this (in addition to the onIndexOutputClosed callback, that made the FSDirectory API crazy). Maybe leave a comment on the Lucene issue to give us feedback that it was already useful :-) |
This class reads the file from the network into a temporary file, and then fsyncs the original file name - which does nothing since the file does not exist and FSDirectory silently ignores syncs on unknown files (fixed in https://issues.apache.org/jira/browse/LUCENE-6150).
The text was updated successfully, but these errors were encountered: