I am creating new topic on this as the old was closed. I increased resources but still I getting this error at some peak hour i have +3000 clients indexing documents using NEST client and i see lot of connection fails with these errors. Is there any config or pool size i have to increase in elastic…

The remote server returned an error: (429) Too Many Requests

agonzalez (Alberto) May 24, 2017, 8:07pm 5

but the cpu is idle most of the time, i dont see any constrain in CPU, why do i need more nodes or cpu?

Also is it better to scale up or scale out? cant i just add more cpus to thee node?

Topic		Replies	Views
ERROR: Too Many Requests - rejected execution of org.elasticsearch.transport.TransportService on EsThreadPoolExecutor Elasticsearch	3	5322	May 15, 2017
In which case ElasticSearch will return 429? Elasticsearch	4	47844	July 6, 2017
Too Many Request 429 Elasticsearch	3	3817	January 25, 2017
Queue Capacity Sizing Elasticsearch	5	2260	July 5, 2017
Response code 429 Logstash	9	9536	July 6, 2017