In which case ElasticSearch will return 429?

Elastic Stack Elasticsearch
1

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d48b8c0f-d033-4490-96ab-9dda50c765ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Hi,

It means that Elasticsearch is not able to keep up with the number of
requests you are sending and that the internal queues are filling up. A
discussion around this can be found in the following blog post:

Best regards,

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c714c352-d903-42b9-87da-dec17c493096%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

Hi,

Thx for your answer!!

However, I still feel confuse because when we keep 200 concurrent thread
cyclically send requests (Indexing request) to cluster，it performence good
and we guess there still have remaining performance space.You can see the
"Throughput" is 5532.8/sec.

https://lh3.googleusercontent.com/-UQLZcDil2kA/VUH-pCKB9qI/AAAAAAAAABQ/YhcqSQp2pqE/s1600/BJG77JSY)J)47MAEPH0IBDX.png

But when we start to test with 300 concurrent thread, there begin to return
error code 429(too many request). It rise 0.66%(4727) errors in 124s.

https://lh3.googleusercontent.com/-d-GAikqdRjQ/VUH_9C7Fj4I/AAAAAAAAABc/2XQi1ZGNc7Y/s1600/WLSH1OK_HNOCIK_51L}AV6W.png
If the 429 error is someway to protect ES server, maybe the queue length
can be longer? Or if we can edit the setting and find the best way to use
ES performance.

Best regards,

Shiny

在 2015年4月30日星期四 UTC+8下午3:58:36，xinm...@163.com写道：

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b44a2dd4-236f-49eb-bfbb-15bd22fb15f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

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+unsubscribe@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.