SevenCss commented on issue #7820: URL: https://github.com/apache/lucene/issues/7820#issuecomment-1685896438
@mikemccand Appreciated for your response. Exactly, after i manually removed the broken one `segments_a7`, the index could recover successfully. However, i'm trying to figure out a way to fix the problem programmatically. Hence, I had a try with `checkindex`, but failed to detect the problem and fix the index. (Then, i found this issue.) I checked the log and have not found any clue that indicates OS or JVM crash happens. Unfortunately, we could not reproduce this issue either. No, we did not deploy our index on a mounted drive. Instead, the index is deployed locally with my program (on windows server). No index replication exists. I also checked the code and found the comments regarding to the Windows issue ( https://github.com/apache/lucene/blob/releases/lucene-solr/8.8.1/lucene/core/src/java/org/apache/lucene/index/IndexFileDeleter.java#L694C1-L707C4 ). However, i'm curious that why we did not print any log, which could provide some hints to end user. It seems that Windows has not plan to fix the OS specific issue, right? -- 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
