-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Empty ES response on search query returning shards 0 #2650
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
Comments
Hello @hawk-roman-rey, this is quite surprising. I don't know how this could happen and I can't help you as I only maintain the Python client and this question is about the server. I would suggest asking in https://discuss.elastic.co/ Thanks for your understanding. |
I fully understand it, what would you suggest to debug this issue on elasticsearch-py side? Are there any ways to enable debug logs or any hacks you could think of? I've posted the question in the elastic forum you suggested, will comment here if something helps |
Something I forgot mentioning:
|
For reference, the Discuss thread is https://discuss.elastic.co/t/elasticsearch-search-query-returning-empty-response-using-elasticsearch-python-api/365983. One thing you could do on the client side is enabling debug logging to be certain that you don't have a bug in your code where sometimes you're not asking for the aggregation. See https://elastic-transport-python.readthedocs.io/en/latest/logging.html for instructions. |
Closing this in favor of the Discuss thread. Thank you! |
I am using elasticsearch py client in my real time application.
The application performs search query aggregations like "sum of field settledAmount in last 10 days".
Most of queries work without problems. However a tiny percent fail silently returning the following.
When the same query is repeated the response is correct containing the aggregations field and the expected value.
I added some retries and it seems to be related with a load problem, since retrying the query without a significant delay (1s) will end in the exact same wrong result.
This is a query example
What might be the reason of elasticsearch returning such "empty response" instead of a "429 status code?"
The text was updated successfully, but these errors were encountered: