# High thread\_pool bulk rejection for specific node

**URL:** <https://discuss.elastic.co/t/high-thread-pool-bulk-rejection-for-specific-node/129850>\
**Category:** Elasticsearch\
**Created:** [April 27, 2018, 3:07pm UTC](https://discuss.elastic.co/t/high-thread-pool-bulk-rejection-for-specific-node/129850 "2018-04-27T15:07:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![igor.leao1](https://avatars.discourse-cdn.com/v4/letter/i/9e8a1a/32.png) [@igor.leao1](https://discuss.elastic.co/u/igor.leao1)\
**Post date:** [April 27, 2018, 3:07pm UTC](https://discuss.elastic.co/t/high-thread-pool-bulk-rejection-for-specific-node/129850/1 "2018-04-27T15:07:54Z")

</div>

Hi there,

A node of my ES cluster, without replication, got lost this night. AWS ASG replaced that node, but it started with a high number of thread\_pool bulk rejection. Injection of all cluster got compromised, though.

The cluster only started to inject data again after excluding this instance from it.

Is this the expected behavior? Can I avoid this somehow?

Some details:  
"version" : {  
"number" : "5.6.5",  
"build\_hash" : "6a37571",  
"build\_date" : "2017-12-04T07:50:10.466Z",  
"build\_snapshot" : false,  
"lucene\_version" : "6.6.1"  
},

Thanks!

---

<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:** [May 25, 2018, 3:07pm UTC](https://discuss.elastic.co/t/high-thread-pool-bulk-rejection-for-specific-node/129850/2 "2018-05-25T15:07:56Z")

</div>

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