# Transport error 429

**URL:** <https://discuss.elastic.co/t/transport-error-429/327528>\
**Category:** Elasticsearch\
**Created:** [March 13, 2023, 7:45am UTC](https://discuss.elastic.co/t/transport-error-429/327528 "2023-03-13T07:45:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Susendiran](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@Susendiran](https://discuss.elastic.co/u/Susendiran)\
**Post date:** [March 13, 2023, 7:45am UTC](https://discuss.elastic.co/t/transport-error-429/327528/1 "2023-03-13T07:45:10Z")

</div>

Hi Team,

We are getting elasticsearch exceptions - transport error 429 while providing es.search command using python pandas for some large set of data(upto 13-15k records). It's showing the limit is more than the threshold. Can you provide a solution to fix this?

Thanks,  
Susendiran

---

<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:** [March 13, 2023, 8:39am UTC](https://discuss.elastic.co/t/transport-error-429/327528/2 "2023-03-13T08:39:14Z")

</div>

How many indices and shards are you actively indexing into?

What bulk size are you using?

How many concurrent indexing threads/processes do you have running?

Which version of Elasticsearch are you using?

What is the size and specification of your cluster?

---

<div class="post-metadata">

**Author:** ![Susendiran](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@Susendiran](https://discuss.elastic.co/u/Susendiran)\
**Post date:** [March 13, 2023, 9:29am UTC](https://discuss.elastic.co/t/transport-error-429/327528/3 "2023-03-13T09:29:33Z")

</div>

Hi @Christian_Dahlqvist ,

We are trying to get some data from two active indices. Please find the screenshots for sizes,

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/b/8b211315f118a04cc32636ff27073a9b25514948.png)

Version of Elasticsearch - 7.5.1

Please find the cluster stats below,  
{  
"\_nodes" : {  
"total" : 1,  
"successful" : 1,  
"failed" : 0  
},  
"cluster\_name" : "elasticsearch",  
"cluster\_uuid" : "z51G64fKROute-83Vaf3iw",  
"timestamp" : 1678699420661,  
"status" : "yellow",  
"indices" : {  
"count" : 665,  
"shards" : {  
"total" : 665,  
"primaries" : 665,  
"replication" : 0.0,  
"index" : {  
"shards" : {  
"min" : 1,  
"max" : 1,  
"avg" : 1.0  
},  
"primaries" : {  
"min" : 1,  
"max" : 1,  
"avg" : 1.0  
},  
"replication" : {  
"min" : 0.0,  
"max" : 0.0,  
"avg" : 0.0  
}  
}  
},  
"docs" : {  
"count" : 22276210,  
"deleted" : 8860566  
},  
"store" : {  
"size\_in\_bytes" : 6115202289  
},  
"fielddata" : {  
"memory\_size\_in\_bytes" : 4099360,  
"evictions" : 0  
},  
"query\_cache" : {  
"memory\_size\_in\_bytes" : 64667297,  
"total\_count" : 34815686,  
"hit\_count" : 11109303,  
"miss\_count" : 23706383,  
"cache\_size" : 20836,  
"cache\_count" : 1231388,  
"evictions" : 1210552  
},  
"completion" : {  
"size\_in\_bytes" : 0  
},  
"segments" : {  
"count" : 2192,  
"memory\_in\_bytes" : 27586819,  
"terms\_memory\_in\_bytes" : 19330907,  
"stored\_fields\_memory\_in\_bytes" : 4451864,  
"term\_vectors\_memory\_in\_bytes" : 0,  
"norms\_memory\_in\_bytes" : 1468800,  
"points\_memory\_in\_bytes" : 1098544,  
"doc\_values\_memory\_in\_bytes" : 1236704,  
"index\_writer\_memory\_in\_bytes" : 1560046,  
"version\_map\_memory\_in\_bytes" : 160,  
"fixed\_bit\_set\_memory\_in\_bytes" : 1224,  
"max\_unsafe\_auto\_id\_timestamp" : -1,  
"file\_sizes" : { }  
}  
},  
"nodes" : {  
"count" : {  
"total" : 1,  
"coordinating\_only" : 0,  
"data" : 1,  
"ingest" : 1,  
"master" : 1,  
"ml" : 1,  
"voting\_only" : 0  
},  
"versions" : [  
"7.5.1"  
],  
"os" : {  
"available\_processors" : 8,  
"allocated\_processors" : 8,  
"names" : [  
{  
"name" : "Linux",  
"count" : 1  
}  
],  
"pretty\_names" : [  
{  
"pretty\_name" : "RHEL",  
"count" : 1  
}  
],  
"mem" : {  
"total\_in\_bytes" : 16656285696,  
"free\_in\_bytes" : 1185083392,  
"used\_in\_bytes" : 15471202304,  
"free\_percent" : 7,  
"used\_percent" : 93  
}  
},  
"process" : {  
"cpu" : {  
"percent" : 9  
},  
"open\_file\_descriptors" : {  
"min" : 3369,  
"max" : 3369,  
"avg" : 3369  
}  
},  
"jvm" : {  
"max\_uptime\_in\_millis" : 39383272420,  
"versions" : [  
{  
"version" : "13.0.1",  
"vm\_name" : "OpenJDK 64-Bit Server VM",  
"vm\_version" : "13.0.1+9",  
"vm\_vendor" : "AdoptOpenJDK",  
"bundled\_jdk" : true,  
"using\_bundled\_jdk" : true,  
"count" : 1  
}  
],  
"mem" : {  
"heap\_used\_in\_bytes" : 785539904,  
"heap\_max\_in\_bytes" : 1037959168  
},  
"threads" : 218  
},  
"fs" : {  
"total\_in\_bytes" : 56882102272,  
"free\_in\_bytes" : 15076413440,  
"available\_in\_bytes" : 15076413440  
},  
"plugins" : ,  
"network\_types" : {  
"transport\_types" : {  
"security4" : 1  
},  
"http\_types" : {  
"security4" : 1  
}  
},  
"discovery\_types" : {  
"zen" : 1  
},  
"packaging\_types" : [  
{  
"flavor" : "default",  
"type" : "tar",  
"count" : 1  
}  
]  
}  
}

---

<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:** [March 13, 2023, 9:40am UTC](https://discuss.elastic.co/t/transport-error-429/327528/4 "2023-03-13T09:40:13Z")

</div>

OK. You have a single node cluster with just 1GB of heap assigned. It seems you are hitting the limit there so probably need to assign more RAM and heap (should be 50% of available RAM).

---

<div class="post-metadata">

**Author:** ![Susendiran](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@Susendiran](https://discuss.elastic.co/u/Susendiran)\
**Post date:** [March 13, 2023, 10:41am UTC](https://discuss.elastic.co/t/transport-error-429/327528/5 "2023-03-13T10:41:45Z")

</div>

upgrading RAM I don't think it's possible from project perspective @Christian_Dahlqvist. Is it possible to clear anything that can free up or any other ways to call it or compressing the size etc.,?

---

<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:** [March 13, 2023, 10:48am UTC](https://discuss.elastic.co/t/transport-error-429/327528/6 "2023-03-13T10:48:31Z")

</div>

A 1GB heap is very small for Elasticsearch, so there is not a lot to play with. It does look like you have a lot of very small shards, which is inefficient and can result in increased overhead. Given the size of your data I would expect a single shard to be able to handle that, so 665 shards is clearly excessive. I would recommend dramatically reducing the number of shards and see what impact thst has.

---

<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:** [April 10, 2023, 10:49am UTC](https://discuss.elastic.co/t/transport-error-429/327528/7 "2023-04-10T10:49:13Z")

</div>

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