# Elasticsearch 1.5.2 shared allocation stuck **URL:** \ **Category:** Elasticsearch\ **Created:** [May 2, 2016, 10:08am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943 "2016-05-02T10:08:02Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![radap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radap/32/8037_2.png) [@radap](https://discuss.elastic.co/u/radap)\ **Post date:** [May 2, 2016, 10:08am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943/1 "2016-05-02T10:08:02Z")
I have a cluster with the following specs (es v 1.5.2): 3 nodes with RAM: 32GB, CPU cores: 8 each 63 total indices = 32 marvel + 1 kibana + 30 data 366 total shards = (32 marvel + 1 kibana + 150 data)\* 1 replica 959,231,444 total docs 588.38GB total data ES\_HEAP\_SIZE=16g I have successfully deleted around 200 **empty indices** and restarted the cluster (didnt disable shard allocation)- normally the allocation take 1 hour to finish but now it is over 12 hours and still I have 183/366 unassigned shared (half!). Also, I can see that node1 have only 6 shards allocated to it- most of the data shards is separated between node2 and node3. I tried to restart node1 and still got the same situation. why isn't it taking more shards to it? And why the allocation is stuck? ---
**Author:** ![radap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radap/32/8037_2.png) [@radap](https://discuss.elastic.co/u/radap)\ **Post date:** [May 2, 2016, 10:49am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943/2 "2016-05-02T10:49:32Z")
Ok, I find a solution- I just [update indices settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-update-settings.html) by setting the number of the replica for all of the indices to 0, then the cluster health turned green and finally updated the settings again by setting the number of the replica for all of the indices back to 1. The cluster started to allocate the shards normally (to node1 also). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 3, 2016, 4:19am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943/3 "2016-05-03T04:19:58Z")
You should really upgrade, 1.5 has a number of known issues. ---
**Author:** ![Rural\_Hunter](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@Rural\_Hunter](https://discuss.elastic.co/u/Rural_Hunter)\ **Post date:** [May 3, 2016, 8:10am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943/4 "2016-05-03T08:10:08Z")
We are also at 1.5.X. Where can I find the list of known issues? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 3, 2016, 9:09pm UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943/5 "2016-05-03T21:09:29Z")
We don't maintain that, by known issues I mean we knew there were problems. Things like allocation improvements in 1.6. From memory, there was a few corruption issues too. ---
**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:54pm UTC](https://discuss.elastic.co/t/elasticsearch-1-5-2-shared-allocation-stuck/48943/6 "2017-07-05T22:54:14Z")