# Strange behaviour of one node in a cluster of 33 nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [February 24, 2020, 9:16am UTC](https://discuss.elastic.co/t/strange-behaviour-of-one-node-in-a-cluster-of-33-nodes/220603 "2020-02-24T09:16:36Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dantonag](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dantonag/32/44130_2.png) [@dantonag](https://discuss.elastic.co/u/dantonag)\ **Post date:** [February 24, 2020, 9:16am UTC](https://discuss.elastic.co/t/strange-behaviour-of-one-node-in-a-cluster-of-33-nodes/220603/1 "2020-02-24T09:16:36Z")
Hello, we have a cluster with 33 nodes (8 of which are data nodes) that shows a strange behaviour on one of the instances (named esdn3\_1-v6). At 1.00 in the night, this instance seems to take almost all the write load of the cluster, and the write queues of the instance fill up to 200. If we stop the node, the load re-balances. You can find attached the node stats, hot threads and tasks when the system is in this state. The configuration files of the various nodes are identical. What may be generating this behaviour? Thanks (I can only upload the log files on wetransfer) [https://wetransfer.com/downloads/7058ce412186e55eb9b532a0c0993b8720200224091535/8c5e034927ea16f331bf347ced41a84220200224091535/ccedcd](https://wetransfer.com/downloads/7058ce412186e55eb9b532a0c0993b8720200224091535/8c5e034927ea16f331bf347ced41a84220200224091535/ccedcd) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 23, 2020, 9:16am UTC](https://discuss.elastic.co/t/strange-behaviour-of-one-node-in-a-cluster-of-33-nodes/220603/2 "2020-03-23T09:16:39Z")
Closed on March 23, 2020, 9:16am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.