# Implications during shrink and force merge on index rollover

**URL:** <https://discuss.elastic.co/t/implications-during-shrink-and-force-merge-on-index-rollover/252712>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [October 20, 2020, 3:55pm UTC](https://discuss.elastic.co/t/implications-during-shrink-and-force-merge-on-index-rollover/252712 "2020-10-20T15:55:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjedynak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjedynak/32/75945_2.png) [@mjedynak](https://discuss.elastic.co/u/mjedynak)\
**Post date:** [October 20, 2020, 3:55pm UTC](https://discuss.elastic.co/t/implications-during-shrink-and-force-merge-on-index-rollover/252712/1 "2020-10-20T15:55:49Z")

</div>

I have index lifecycle policy (hot phase 1 month -\> warm phase, read only) and during rollover there is automatic operation of shrink and force merge.  
My index has 2 primary shards + 1 replica (after shrinking it's 1 primary + 1 replica).  
Shrinking and merging operations for index that has many documents can take significant amount of time.

Is the index being rolled over during that time searchable? (I think it should be as replica is not touched but search performance might be lower)

What are other implications if such operation takes long time?

---

<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 17, 2020, 3:56pm UTC](https://discuss.elastic.co/t/implications-during-shrink-and-force-merge-on-index-rollover/252712/2 "2020-11-17T15:56:05Z")

</div>

Closed on November 17, 2020, 3:56pm UTC

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