# After node replacement, rate of (re) initializing shards is decreasing **URL:** \ **Category:** Elasticsearch\ **Created:** [September 11, 2019, 8:11pm UTC](https://discuss.elastic.co/t/after-node-replacement-rate-of-re-initializing-shards-is-decreasing/199141 "2019-09-11T20:11:39Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Philip\_Brown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/philip_brown/32/49853_2.png) [@Philip\_Brown](https://discuss.elastic.co/u/Philip_Brown)\ **Post date:** [September 11, 2019, 8:11pm UTC](https://discuss.elastic.co/t/after-node-replacement-rate-of-re-initializing-shards-is-decreasing/199141/1 "2019-09-11T20:11:39Z")
I started off replacing a node, and having 1200 unassigned shards. The cluster happily started reassigning 8 shards at a time. Then it hit somewhere under 1000 shards unassigned.. and suddenly, started to only do 4 shards at a time. Um, what? Might anyone have insight into why this is happening, and more importantly, how to fix it? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 14, 2019, 10:35am UTC](https://discuss.elastic.co/t/after-node-replacement-rate-of-re-initializing-shards-is-decreasing/199141/2 "2019-09-14T10:35:39Z")
There is a limit per node, so if fewer nodes are involved at this point it could lead to fewer concurrent recoveries. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 12, 2019, 10:35am UTC](https://discuss.elastic.co/t/after-node-replacement-rate-of-re-initializing-shards-is-decreasing/199141/3 "2019-10-12T10:35:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.