-
Notifications
You must be signed in to change notification settings - Fork 1.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
[BUG]"type": "index_out_of_bounds_exception", "reason": "index_out_of_bounds_exception: null" #8155
Comments
Trying to understand, what are you querying? How do I reproduce this problem? |
When querying an OpenSearch get the following exception in OS 2.5 { def expires_at = doc["variant.test_result.expires_at"]; def score = 0; if (has_test && boost_test && expires_at.value.toInstant().toEpochMilli() > params.now ) { def owner_priority = doc["owner_priority"]; if (has_priority) { return score + _score; return _score; Analysis: It appears that there are two related issues on ElasticSearch that seem to potentially fix this issue. |
The core of the problem looks like is caused by adding the min_score: 1 |
@adiOpenSearch could you please edit your issue with instructions of the smallest possible repro for what does look like a bug? try to reduce the query to the absolute minimum one Next, if you want to help fixing, start by writing a REST test for it? https://github.com/opensearch-project/OpenSearch/blob/main/TESTING.md#testing-the-rest-layer |
@adiOpenSearch are you able to work on @dblock's suggestion? do you need any help/guidance on this? |
@macohen Unfortunately this error has only been tracked happening on production cluster. Not able to reproduce it locally or on any pre-production environment. This issue only happens on a subset of queries, these queries are also known to break consistently for a period of time then inexplicably start working on their own. |
@adiOpenSearch -- based on the stack trace, this almost sounds like index corruption (which tends to be unlikely). Is this happening on a single index? Or does it happen across multiple indices? If it's a single index, then it sounds like the norms for one of the segments was written incorrectly (and maybe can be repaired). |
@msfroh This issue is on single index for now and against a particular query. And rolled index multiple times. |
@noCharger -- We determined this was caused by The exception comes because the OpenSearch/server/src/main/java/org/opensearch/common/lucene/search/function/MinScoreScorer.java Lines 98 to 103 in a9ce180
|
Exception - index_out_of_bounds_exception: null
When querying an OpenSearch get the following exception:
{
"error": {
"root_cause": [
{
"type": "index_out_of_bounds_exception",
"reason": "index_out_of_bounds_exception: null"
"script_stack": [
"java.base/java.nio.Buffer.checkIndex(Buffer.java:687 )",
"java.base/java.nio.DirectByteBuffer.get(DirectByteBuffer.java:269 )",
"org.apache.lucene.store .ByteBufferGuard.getByte(ByteBufferGuard.java:119 )",
"org.apache.lucene.store .ByteBufferIndexInput$SingleBufferImpl.readByte(ByteBufferIndexInput.java:564 )",
"org.apache.lucene.codecs.lucene90.Lucene90NormsProducer$8.longValue(Lucene90NormsProducer.java:442 )",
"org.apache.lucene.search .LeafSimScorer.getNormValue(LeafSimScorer.java:47 )",
"org.apache.lucene.search .LeafSimScorer.score(LeafSimScorer.java:60 )",
"org.apache.lucene.search .SynonymQuery$SynonymScorer.score(SynonymQuery.java:548 )",
"org.apache.lucene.search .ConjunctionScorer.score(ConjunctionScorer.java:61 )",
"org.apache.lucene.search .DisjunctionSumScorer.score(DisjunctionSumScorer.java:41 )",
"org.apache.lucene.search .DisjunctionScorer.score(DisjunctionScorer.java:193 )",
"org.apache.lucene.search .ConjunctionScorer.score(ConjunctionScorer.java:61 )",
"org.apache.lucene.search .ReqOptSumScorer.score(ReqOptSumScorer.java:263 )",
"org.opensearch.script.ScoreScript.lambda$setScorer$4(ScoreScript.java:156 )",
"org.opensearch.script.ScoreScript.get_score(ScoreScript.java:168 )",
"def ",
"^---- HERE"
Expected behavior
The fix of this issue is not in both 2.5 and 2.7 version. Can it be fixed in the next release version 2.9.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: