You should drop your heap to 31GB, look for java pointer compression if you
want to know more.

If your threadpools are filling up then your node is overloaded and you
need more nodes. Take a look at
http://www.elastic.co/guide/en/elasticsearch/guide/current/_don_8217_t_touch_these_settings.html#_threadpools

On 29 March 2015 at 02:09, Ayman <aymanshor...@gmail.com> wrote:

> Hi there,
>
> Recently i have built elasticsearch with fluentd and Kibana and all is
> working fine, but we are facing high cpu load while performing search
> caused
> by java.
>
> I have 60 GB Ram and 16 processors and each processor has 2 cores.
>
> ES_HEAP_SIZE=32g
> -find below more details
>
>  curl "localhost:9200/_cat/thread_pool?v&h=search.rejected"
> search.rejected
>             387
>
> curl "localhost:9200/_cat/thread_pool?v&h=index.rejected"
> index.rejected
>              0
>  - snapshot from elasticsearch.log
>
> [DEBUG][action.search.type       ] [Hulk 2099] [logstash-2015.03.14][4],
> node[qxcAN3lURs65Lf1GMhB_qg], [P], s[STARTED]: Failed to execute
> [org.elasticsearch.action.search.SearchRequest@7c71025f] lastShard [true]
> org.elasticsearch.common.util.concurrent.EsRejectedExecutionException:
> rejected execution (queue capacity 1000) on
> org.elasticsearch.search.action.SearchServiceTransportAction$23@1d7c9f0f
>         at
>
> org.elasticsearch.common.util.concurrent.EsAbortPolicy.rejectedExecution(EsAbortPolicy.java:62)
>         at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821)
>         at
>
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372)
>         at
>
> org.elasticsearch.search.action.SearchServiceTransportAction.execute(SearchServiceTransportAction.java:551)
>         at
>
> org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQuery(SearchServiceTransportAction.java:228)
>         at
>
> org.elasticsearch.action.search.type.TransportSearchCountAction$AsyncAction.sendExecuteFirstPhase(TransportSearchCountAction.java:71)
>         at
>
> org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:171)
>
> Now i read that i have to update the threadpool settings in ES and i have
> now
>  curl -XGET localhost:9200/_cluster/settings?pretty
> {
>   "persistent" : { },
>   "transient" : { }
> }
>
> i'm trying to update the settings with the below commands
>
> curl -XPUT localhost:9200/_cluster/settings -d '{
>
> "threadpool" : {
>   "index": {
>     "type": "fixed",
>     "size": 32,
>     "queue_size": 1000
>   },
>   "bulk": {
>     "type": "fixed",
>     "size": 32,
>     "queue_size": 1000
>   },
>   "search": {
>     "type": "fixed",
>     "size": 96,
>     "queue_size": 1000
>  }
> }
> }'
>
> but i keep getting {"error":"ActionRequestValidationException[Validation
> Failed: 1: no settings to update;]","status":400}
>
>
> What's wrong with this command? is it the right solution for my issue ?
>
> Please advise
>
> Thanks.
>
> Ayman
>
>
>
> --
> View this message in context:
> http://elasticsearch-users.115913.n3.nabble.com/Add-non-existing-settings-in-cluster-settings-in-elasticsearch-tp4072768.html
> Sent from the ElasticSearch Users mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/1427555353485-4072768.post%40n3.nabble.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9ZJm_iXOA7%2B83EsLsoE7%2Bk%3DUg1rMWnY_fa2it_BNuePw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to