dweiss commented on issue #14334: URL: https://github.com/apache/lucene/issues/14334#issuecomment-2772129998
There has to be a certain trust in what the operating system provides and its consistency guarantees. What you describe seems like a fringe case that - even if possible - falls under the tiny, tiny fraction of possibilities that can end up corrupting your index. The tradeoff here is making everything else potentially slower for the 99.99% of other cases. Let's not be paranoid. It's not possible to fix such low-level corner cases from Java level. Put some monitoring on remaining disk space, add an UPS and ECC memory. Should get you a long way in dodging these scenarios. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
