# 5.4.0 Relocation of shards on the node affects indexing of data on the node

**URL:** <https://discuss.elastic.co/t/5-4-0-relocation-of-shards-on-the-node-affects-indexing-of-data-on-the-node/156416>\
**Category:** Elasticsearch\
**Created:** [November 13, 2018, 8:44am UTC](https://discuss.elastic.co/t/5-4-0-relocation-of-shards-on-the-node-affects-indexing-of-data-on-the-node/156416 "2018-11-13T08:44:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neha\_Sharma1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/neha_sharma1/32/36504_2.png) [@Neha\_Sharma1](https://discuss.elastic.co/u/Neha_Sharma1)\
**Post date:** [November 13, 2018, 8:44am UTC](https://discuss.elastic.co/t/5-4-0-relocation-of-shards-on-the-node-affects-indexing-of-data-on-the-node/156416/1 "2018-11-13T08:44:57Z")

</div>

I have 7 data nodes with 2.0TB on each node. On particular index, which has all the primary shards on say Node A ,has high indexing rate. Whenever a shard of any index is relocated from Node A to any other node, the indexing rate slows down and it seems as if the indexing has stopped.

How can I configure ES such that relocation does not affect my indexing of data.

---

<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:** [December 11, 2018, 8:45am UTC](https://discuss.elastic.co/t/5-4-0-relocation-of-shards-on-the-node-affects-indexing-of-data-on-the-node/156416/2 "2018-12-11T08:45:02Z")

</div>

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