# ELS 1.7 hotspot issues with shard allocation

**URL:** <https://discuss.elastic.co/t/els-1-7-hotspot-issues-with-shard-allocation/36484>\
**Category:** Elasticsearch\
**Created:** [December 7, 2015, 1:18am UTC](https://discuss.elastic.co/t/els-1-7-hotspot-issues-with-shard-allocation/36484 "2015-12-07T01:18:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VB1](https://avatars.discourse-cdn.com/v4/letter/v/2acd7d/32.png) [@VB1](https://discuss.elastic.co/u/VB1)\
**Post date:** [December 7, 2015, 1:18am UTC](https://discuss.elastic.co/t/els-1-7-hotspot-issues-with-shard-allocation/36484/1 "2015-12-07T01:18:41Z")

</div>

We are using ELS 1.7 version primarily with gray log to for our logging datastore with multiple indexes.

We have 6 node cluster with all nodes as data + master.  
We are seeing issues when one of them node goes down and we bring another node in the cluster then new node gets most of the shards and that node becomes hot spot.

Any help will be greatly appreciated.

Regards,  
VB.

---

<div class="post-metadata">

**Author:** ![VB1](https://avatars.discourse-cdn.com/v4/letter/v/2acd7d/32.png) [@VB1](https://discuss.elastic.co/u/VB1)\
**Post date:** [December 7, 2015, 9:57pm UTC](https://discuss.elastic.co/t/els-1-7-hotspot-issues-with-shard-allocation/36484/2 "2015-12-07T21:57:39Z")

</div>

Any help on this please

---

<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:** [July 5, 2017, 11:32pm UTC](https://discuss.elastic.co/t/els-1-7-hotspot-issues-with-shard-allocation/36484/3 "2017-07-05T23:32:58Z")

</div>