The new setting of bounded bulk queue is a precaution not to overwhelm the
internal ES buffers.

Unbounded queue size is potentially dangerous since your node operations
may get stalled by too many bulk requests.

You could increase bulk queue_size from 50 to 100 if that works better.
But, the soundest method is to check your bulk indexing code for capping
the number of concurrent bulk requests. Or you may increase the number of
nodes/shards. Right now it seems your concurrency setting is too high for
the capacity of your cluster (just a wild guess, without knowing your
numbers).

Jörg

On Fri, Jan 31, 2014 at 6:48 AM, Ramchandra Phadake <
ramchandra.phad...@gmail.com> 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 elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/89c6e465-c23f-4234-9667-cd09be4a7178%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAKdsXoExvP3W-6MiR%3DSG_c%2BR9kJz_koLLq8zOF_JML_axhrQbw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to