-
-
Notifications
You must be signed in to change notification settings - Fork 599
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
Queue capacity #301
Comments
Hi @christopher5106, this type of question is actually more suited to the Elasticsearch mailing list or IRC. The error you receive indicates you're overloading the server with queries. |
Ok thank you Karmi, just wanted to know if the cookbook would be for anything in this case. Thanks! |
@christopher5106 No, unfortunately the cookbook doesn't add anything for that. One way or another you need to increase the capacity, or throttle the request rate (but that's already happening with this error on the ES side)... |
What I don't understand is why I can got up to a queue of 1000 when I have On Fri, Feb 20, 2015 at 5:38 PM, Karel Minarik [email protected]
|
I'm having the following problem :
"SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[rlrweRJAQJqaoKfFB8il5A][stt_prod][3]: EsRejectedExecutionException[rejected execution (queue capacity 1000) on org.elasticsearch.action.search.type.TransportSearchTypeAction
It sounds very strange; when I restarted the server, it worked fine again.
What could happen ?
Here is my configuration :
5320 elastic+ 20 0 9.918g 4.788g 72980 S 7.6 65.3 29:49.42 java
My traffic is not more than 125 requests per minutes :
So if I understand well, each request can live 30s, how come I have a queue of 1000 ?!
Can ES save the requests in the queue while the shards have failed ?
Why do the shards do not come back ?
Thanks for your help (I'm not using ES usually, more Solr or CloudSearch)
The text was updated successfully, but these errors were encountered: