# Shrink API sets index.allocation.max.retries to 1?

**URL:** <https://discuss.elastic.co/t/shrink-api-sets-index-allocation-max-retries-to-1/152856>\
**Category:** Elasticsearch\
**Created:** [October 17, 2018, 2:02pm UTC](https://discuss.elastic.co/t/shrink-api-sets-index-allocation-max-retries-to-1/152856 "2018-10-17T14:02:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cdekker](https://avatars.discourse-cdn.com/v4/letter/c/f05b48/32.png) [@cdekker](https://discuss.elastic.co/u/cdekker)\
**Post date:** [October 17, 2018, 2:02pm UTC](https://discuss.elastic.co/t/shrink-api-sets-index-allocation-max-retries-to-1/152856/1 "2018-10-17T14:02:12Z")

</div>

I just noticed my ES 6.2.4 cluster not recovering from yellow after a recent node failure. Some shards would remain unassigned.

Upon closer inspection, the affected indices had `index.allocation.max_retries` set to 1, which was apparently a side effect of a Shrink operation I ran a week ago.

Why is this parameter being set by Shrink?  
Resetting it to null made the cluster instantly recover the shards back to green.  
Is there any harm in doing so?  
Are there any other hidden settings that Shrink leaves behind that I should know about?

---

<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:** [November 14, 2018, 2:13pm UTC](https://discuss.elastic.co/t/shrink-api-sets-index-allocation-max-retries-to-1/152856/2 "2018-11-14T14:13:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.