# Rally benchmarking Elasticsearch with 429 error code

**URL:** <https://discuss.elastic.co/t/rally-benchmarking-elasticsearch-with-429-error-code/276917>\
**Category:** Elasticsearch\
**Created:** [June 24, 2021, 10:58am UTC](https://discuss.elastic.co/t/rally-benchmarking-elasticsearch-with-429-error-code/276917 "2021-06-24T10:58:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![parallelism](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@parallelism](https://discuss.elastic.co/u/parallelism)\
**Post date:** [June 24, 2021, 10:58am UTC](https://discuss.elastic.co/t/rally-benchmarking-elasticsearch-with-429-error-code/276917/1 "2021-06-24T10:58:11Z")

</div>

Hello,

We are testing a new Elasticsearch cluster with Rally. The indexing task is getting an error rate greater than zero and we also found that the total number of indexed documents does not match the target number of the track.

In the "rally.log" file, we found a 429 code response on some requests:

`2021-06-23 15:00:38,463 -not-actor-/PID:91 elasticsearch WARNING POST http://elasticsearch-data:9200/_bulk [status:429 request:0.241s]`

However, Elasticsearch node logs does not register rejected requests.  
According to other posts, Elasticsearch logs "rejected execution" when error 429 occurs, is it true?

Our Elasticsearch cluster is deployed into a proxied and balanced installation, and we suspect the 429 error could be coming from these components.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 3, 2021, 6:11pm UTC](https://discuss.elastic.co/t/rally-benchmarking-elasticsearch-with-429-error-code/276917/2 "2021-07-03T18:11:18Z")

</div>

> [@parallelism](#):
>
> Our Elasticsearch cluster is deployed into a proxied and balanced installation, and we suspect the 429 error could be coming from these components.

In that case I would recommend running the same benchmark directly against the cluster and compare results.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 31, 2021, 6:11pm UTC](https://discuss.elastic.co/t/rally-benchmarking-elasticsearch-with-429-error-code/276917/3 "2021-07-31T18:11:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.