Skip to content
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

Closed
christopher5106 opened this issue Feb 20, 2015 · 4 comments
Closed

Queue capacity #301

christopher5106 opened this issue Feb 20, 2015 · 4 comments

Comments

@christopher5106
Copy link

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 :

  • ES version is 1.0.1
  • I have 3 indexes, of respective size 2.5G, 1.7G and 250M, each one has 5 shards
  • the cluster is one only one instance (solo)
  • the state of the cluster says 15 successful shard, 0 failed shard and 30 total shards (where are the 15 shards missing ?)
  • in my settings, mlockall is set to true
  • I enabled script.disable_dynamic: false, installed plugins _head and action-updatebyquery
  • ES heap size is correctly set to 50% by the recipe which I can confirm using top command :
    5320 elastic+ 20 0 9.918g 4.788g 72980 S 7.6 65.3 29:49.42 java
  • I'm using only 30% of disk capacity

My traffic is not more than 125 requests per minutes :
requests

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)

@karmi
Copy link
Contributor

karmi commented Feb 20, 2015

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.

@christopher5106
Copy link
Author

Ok thank you Karmi, just wanted to know if the cookbook would be for anything in this case.

Thanks!

@karmi
Copy link
Contributor

karmi commented Feb 20, 2015

@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)...

@christopher5106
Copy link
Author

What I don't understand is why I can got up to a queue of 1000 when I have
200 requests / minute ?!

On Fri, Feb 20, 2015 at 5:38 PM, Karel Minarik notifications@github.com
wrote:

@christopher5106 https://github.com/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)...


Reply to this email directly or view it on GitHub
#301 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants