using cached for both index and search thread pool?
curl -XPUT localhost:9200/_cluster/settings -d '{
"persistent" : {
"threadpool.index.type" : "cached",
"threadpool.search.type" : "cached"
}
}'
On Monday, April 28, 2014 5:40:14 PM UTC+8, Le Thanh Nguyen wrote:
>
> Hi,
>
> we have the same problem with ES 1.1.0
>
> Increase only queue_size could resolve the problem? Anything else?
>
> We have 30 concurrent bulk but not on the same document, each bulk
> contains about 30 documents.
>
> See also :
> https://github.com/richardwilly98/elasticsearch-river-mongodb/issues/223
>
> On Friday, January 31, 2014 6:48:31 AM UTC+1, Ramchandra Phadake wrote:
>>
>> Hi,
>>
>> Recently we migrated from 0.90.1 to 0.90.9. We did change
>> index.codec.bloom.load=false initially but even with true we obsetve same
>> behaviour.
>> Nothing else has changed from indexing code. We are using bulk API. Any
>> pointers why we can get EsRejectedExecutionException?
>> This doesn't frequently in indexing process.
>>
>> We did try by setting with few thousand size but this exception comes but
>> rarely.
>> After setting bulk queue to -1 it appears to be working. -1 means
>> unbounded size so is it safe to set to -1.
>>
>> Thanks,
>> Ram
>>
>>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2233852a-2afe-4eb0-b0cf-6816c6e84602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
