# Problems after node restart **URL:** \ **Category:** Elasticsearch\ **Created:** [August 16, 2016, 9:47pm UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194 "2016-08-16T21:47:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Maxwell\_Flanders](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@Maxwell\_Flanders](https://discuss.elastic.co/u/Maxwell_Flanders)\ **Post date:** [August 16, 2016, 9:47pm UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194/1 "2016-08-16T21:47:15Z")
After a data node in our cluster (3master, 7data, 3client nodes) died recently, it appears from running out of memory due to field data usage, we added two data nodes, and restarted the one that died. After a couple hours, our cluster was approaching green and got down to a single shard. However, that single shard will not seem to finish and is stuck in INITIALIZING mode. It is one of the daily shards dated to today. Is there anything I can do to force this shard onto a node, or restart its initialization process?? Additionally, it seems that our cluster isn't really re-balancing or distributing its load onto the new data nodes. Here is a screenshot of our marvel display, as you can see, the load is _extremely_ unbalanced across our data nodes. Is this something that should just balance out over time?? ![](https://us1.discourse-cdn.com/elastic/original/2X/8/8ec078eebcb7f629f08387d5399871fce8034ac2.png) ---
**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:** [August 16, 2016, 10:43pm UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194/2 "2016-08-16T22:43:19Z")
Check `_cat/recovery` for that one shard, and `_cat/tasks` to see if any reallocations are pending. ---
**Author:** ![Maxwell\_Flanders](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@Maxwell\_Flanders](https://discuss.elastic.co/u/Maxwell_Flanders)\ **Post date:** [August 16, 2016, 10:51pm UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194/3 "2016-08-16T22:51:31Z")
It does show in recovery: `logs-2016.08.16 4 3539791 replica index 10.25.250.37 10.25.250.43 n/a n/a 82 86.6% 7422192764 71.6% 82 7422192764 0 0.0% 27723` and the tasks api call is actually throwing an error.... ``` { "error" : { "root_cause" : [ { "type" : "illegal_argument_exception", "reason" : "No feature for name [tasks]" } ], "type" : "illegal_argument_exception", "reason" : "No feature for name [tasks]" }, "status" : 400 } ``` ---
**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:** [August 16, 2016, 11:14pm UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194/4 "2016-08-16T23:14:57Z")
What version are you on? With the replica, keep an eye on that `_cat` endpoint as the first and second percentage values should be increasing. ---
**Author:** ![Maxwell\_Flanders](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@Maxwell\_Flanders](https://discuss.elastic.co/u/Maxwell_Flanders)\ **Post date:** [August 26, 2016, 2:21am UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194/5 "2016-08-26T02:21:12Z")
Just a follow up on this, that one shard DID in fact eventually allocate. It just blew my mind because it took around 3 hours for that one 8G shard to process, which was extremely unprecedented, since the rest of our database (2+ TB) had managed to re-allocate over the course of the day. It did finish however and our cluster is back together. Thank you mark! The advice was very helpful. ---
**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:25pm UTC](https://discuss.elastic.co/t/problems-after-node-restart/58194/6 "2017-07-05T22:25:04Z")