High thread_pool bulk rejection for specific node

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"


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