# Upgrading version in a cluster with closed indices

**URL:** <https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798>\
**Category:** Elasticsearch\
**Created:** [April 29, 2016, 11:32am UTC](https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798 "2016-04-29T11:32:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lobsterdore](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lobsterdore/32/9482_2.png) [@lobsterdore](https://discuss.elastic.co/u/lobsterdore)\
**Post date:** [April 29, 2016, 11:32am UTC](https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798/1 "2016-04-29T11:32:41Z")

</div>

I've just given the Elasticsearch migration plugin a whirl on an ELK stack, I have lots of closed indices containing historical log data so I get a lot of ancient index warnings.

If I want to upgrade (in my case from 1.7 to 2.x) would it be prudent to reopen all closed indices? Or do I just need to open them and check if they are viable using the migration plugin?

---

<div class="post-metadata">

**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 1, 2016, 1:33am UTC](https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798/2 "2016-05-01T01:33:42Z")

</div>

I would reopen them (one by one or rolling) and run the migration plugin again.

---

<div class="post-metadata">

**Author:** ![lobsterdore](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lobsterdore/32/9482_2.png) [@lobsterdore](https://discuss.elastic.co/u/lobsterdore)\
**Post date:** [May 5, 2016, 8:31am UTC](https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798/3 "2016-05-05T08:31:06Z")

</div>

That makes sense, I could open up a bunch at once, scan then fix.

---

<div class="post-metadata">

**Author:** ![rusty](https://avatars.discourse-cdn.com/v4/letter/r/f17d59/32.png) [@rusty](https://discuss.elastic.co/u/rusty)\
**Post date:** [May 5, 2016, 8:35am UTC](https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798/4 "2016-05-05T08:35:46Z")

</div>

You should also disable shard rebalance in cluster while opening such closed indexes (because ES may try automatically rebalance them).

---

<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:** [July 5, 2017, 10:53pm UTC](https://discuss.elastic.co/t/upgrading-version-in-a-cluster-with-closed-indices/48798/5 "2017-07-05T22:53:49Z")

</div>