# Slow node recovery in ElasticSearch 2.3.3

**URL:** <https://discuss.elastic.co/t/slow-node-recovery-in-elasticsearch-2-3-3/55570>\
**Category:** Elasticsearch\
**Created:** [July 14, 2016, 9:41pm UTC](https://discuss.elastic.co/t/slow-node-recovery-in-elasticsearch-2-3-3/55570 "2016-07-14T21:41:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_D\_Ament](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_d_ament/32/764_2.png) [@John\_D\_Ament](https://discuss.elastic.co/u/John_D_Ament)\
**Post date:** [July 14, 2016, 9:41pm UTC](https://discuss.elastic.co/t/slow-node-recovery-in-elasticsearch-2-3-3/55570/1 "2016-07-14T21:41:44Z")

</div>

We have a small 3 node cluster. Two indices, .scripts and our own index.

```
size: 65.2Mi (65.2Mi)
docs: 18,447 (18,447)

```

We have 679 aliases on the single index. In total, we have 15 shards in one index and 3 shards in the other. The boxes are using 5gb heap and have total 8 gb per box (host: CentOS 6.6, VMs out in AWS)

The recovery time starting today has dropped dramatically. Yesterday its fine, and in smaller environments its fine as well. So I was wondering, is this just too much data? The rebalancing of the shards took about 35 minutes.

---

<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, 10:35pm UTC](https://discuss.elastic.co/t/slow-node-recovery-in-elasticsearch-2-3-3/55570/2 "2017-07-05T22:35:26Z")

</div>