# Primay shards on the same node caused load unbalanced

**URL:** https://discuss.elastic.co/t/primay-shards-on-the-same-node-caused-load-unbalanced/165205
**Category:** Elasticsearch
**Created:** [January 22, 2019, 9:52am UTC](https://discuss.elastic.co/t/primay-shards-on-the-same-node-caused-load-unbalanced/165205 "2019-01-22T09:52:53Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![shiloong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiloong/32/44625_2.png) [@shiloong](https://discuss.elastic.co/u/shiloong)
#### Post date: [January 22, 2019, 9:52am UTC](https://discuss.elastic.co/t/primay-shards-on-the-same-node-caused-load-unbalanced/165205/1 "2019-01-22T09:52:53Z")

</div>

My cluster have 4 data nodes, and this caused many bulk rejections,we didn't have any update operate,Elasticsearch version is 6.4.0

> GET \_cat/shards?v&index=_2019.01.22_&h=index,shared,prirep,stat,node  
> index prirep node  
> xxx\_accounting-2019.01.22 p jdB9njq  
> xxx\_accounting-2019.01.22 r an8XFEI  
> filebeat-syslog-2019.01.22 r M8bpmYn  
> filebeat-syslog-2019.01.22 p jdB9njq  
> filebeat-syslog-2019.01.22 p jdB9njq  
> filebeat-syslog-2019.01.22 r an8XFEI  
> filebeat-syslog-2019.01.22 r CrBTwW6  
> filebeat-syslog-2019.01.22 p jdB9njq  
> xxx\_messages-2019.01.22 r CrBTwW6  
> xxx\_messages-2019.01.22 p jdB9njq  
> metricbeat-login-2019.01.22 p jdB9njq  
> metricbeat-login-2019.01.22 r an8XFEI  
> metricbeat-xcompute-2019.01.22 p jdB9njq  
> metricbeat-xcompute-2019.01.22 r an8XFEI  
> metricbeat-compute-2019.01.22 r M8bpmYn  
> metricbeat-compute-2019.01.22 p jdB9njq  
> metricbeat-compute-2019.01.22 p jdB9njq  
> metricbeat-compute-2019.01.22 r an8XFEI  
> metricbeat-compute-2019.01.22 r CrBTwW6  
> metricbeat-compute-2019.01.22 p jdB9njq  
> metricbeat-compute-2019.01.22 p jdB9njq  
> metricbeat-compute-2019.01.22 r an8XFEI  
> metricbeat-compute-2019.01.22 p jdB9njq  
> metricbeat-compute-2019.01.22 r an8XFEI  
> auditbeat-6.5.4-2019.01.22 r M8bpmYn  
> auditbeat-6.5.4-2019.01.22 p jdB9njq  
> auditbeat-6.5.4-2019.01.22 p jdB9njq  
> auditbeat-6.5.4-2019.01.22 r an8XFEI

the thread pool info

> curl localhost:9200/\_cat/thread\_pool?v | grep jdB9njq  
> dB9njq analyze 0 0 0  
> jdB9njq fetch\_shard\_started 0 0 0  
> jdB9njq fetch\_shard\_store 0 0 0  
> jdB9njq flush 0 0 0  
> jdB9njq force\_merge 0 0 0  
> jdB9njq generic 0 0 0  
> jdB9njq get 0 0 0  
> jdB9njq index 0 0 0  
> jdB9njq listener 0 0 0  
> jdB9njq management 1 0 0  
> jdB9njq refresh 1 0 0  
> jdB9njq search 0 0 0  
> jdB9njq snapshot 0 0 0  
> jdB9njq warmer 0 0 0  
> jdB9njq write 48 165 7591394

---

<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: [February 19, 2019, 9:52am UTC](https://discuss.elastic.co/t/primay-shards-on-the-same-node-caused-load-unbalanced/165205/2 "2019-02-19T09:52:56Z")

</div>

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