-
Notifications
You must be signed in to change notification settings - Fork 72
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] Hybrid query returned error "e_o_f_exception read past EOF" #964
Comments
tried one more set of steps that involve custom analyzer for korean language `nori' https://mvnrepository.com/artifact/org.opensearch.plugin/analysis-nori and much simpler query:
got same type of response, and found following stacktrace in the log
few things to notice:
|
@martin-gaievski Can you share the index configuration you used for reproducing the bug? |
@vibrantvarun yes, I'm using following config for index and ingest pipeline:
pipeline
I'm using bedrock text embeddings model with 1536 dimensions, but I suspect that's not a critical piece, you should see the issue with any other model |
Following steps can be taken to reproduce issue in local cluster using open source version and local model. It involves some manual tweaks related to manual installation of This is developer setup, you need to have neural-search repository locally, check Dev guide for details Getting artifacts for
Step to reproduce error
You'll get the response with EOF error, something like
|
Fix has been merged to 2.x and main, we're on track for 2.19 |
@martin-gaievski Is there a workaround available while we wait for the 2.19 release? |
the only workaround I think think of is to redesign the query and get rid of |
Thank you! |
What is the bug?
When running hybrid query with a certain complex structure then response contains failures for some shards:
it may be the issue similar to one reposted for 2.13: #621
How can one reproduce the bug?
for index with text based documents run a hybrid query with a following structure:
below is example of response :
What is your host/environment?
We tested in OS 2.15 and latest main. Same query works correctly in 2.13
Do you have any additional context?
Looks like issue depends on number of documents that are present in the index. Same query works fine with ~20K documents but start failing with 40K documents. My guess it's related to some optimization techniques in one of sub-queries.
The text was updated successfully, but these errors were encountered: