-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Hit java.lang.IndexOutOfBoundsException in es log after recent Lucene9 snapshot upgrade #78785
Comments
Pinging @elastic/es-search (Team:Search) |
@wwang500 Thanks for reporting this, it's bad that Lucene can corrupt indices like that. Do you know when you saw the first instance of this bug, was it only after the latest Lucene snapshot upgrade? |
Wei told me that the first time this was seen was in ML QA build 9772 (that's on an internal Jenkins server) and the Elasticsearch commit that was built from was 5964ffe7df6841. So the problem pre-dates #78286, and was most likely introduced by #73324. |
I opened https://issues.apache.org/jira/browse/LUCENE-10159 since this is most likely a Lucene issue. |
Would it be possible to get a zip file containing the index that triggered this exception? This would allow us to introspect the content of the index files to better understand what got wrong with this corrupt segment. |
Zip files have been sent out to @dnhatn . |
I've opened apache/lucene#389. |
Recently, (after #78286 and #73324 merge), one of ml nightly test failed with java.lang.IndexOutOfBoundsException in es log.
Part of es.log:
It happened only on 8.0 branch.
The text was updated successfully, but these errors were encountered: