Re: Delete by query fails often with HTTP 503

2014-03-18 Thread Thomas S.
Thanks Clint, We have two nodes with 60 shards per node. I will increase the queue size. Hopefully this will reduce the amount of rejections. Thomas On Tuesday, March 18, 2014 6:11:27 PM UTC+1, Clinton Gormley wrote: > > Do you have lots of shards on just a few nodes? Delete by query is handle

Re: Delete by query fails often with HTTP 503

2014-03-18 Thread Clinton Gormley
Do you have lots of shards on just a few nodes? Delete by query is handled by the `index` thread pool, but those threads are shared across all shards on a node. Delete by query can produce a large number of changes, which can fill up the thread pool queue and result in rejections. You can either

Delete by query fails often with HTTP 503

2014-03-18 Thread Thomas S.
Hi, We often get failures when using the delete by query API. The response is an HTTP 503 with a body like this: {"_indices": {"myindex": {"_shards": {"successful": 2, "failed": 58, "total": 60 Is there a way to figure out what is causing this error? It seems to mostly happen when the sea