Hi, As explained in the blog post, increasing the queue size will not improve performance, just make you store more data in memory on the cluster awaiting processing. It could actually instead end up reducing performance. It looks like you are hitting the limit of your cluster and that the number of concurrent indexers it is able to keep up with is somewhere between 200 and 300.
Have you been able to identify what is limiting performance when the queues start building up and Elasticsearch can't keep up? Christian On Thursday, April 30, 2015 at 8:58:36 AM UTC+1, xinm...@163.com wrote: > > When doing pressure test on ES cluster，it sometimes may return 429(too > many request). > > I can't find any detail docs about this.In which case ElasticSearch may > return 429 ? > > -- 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/fe10519c-e1cc-4ec3-b703-3990ba0393bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
