# IndexFormatTooNewException after bringing node upgraded 2.0.0 -\> 2.3.2 into cluster

**URL:** <https://discuss.elastic.co/t/indexformattoonewexception-after-bringing-node-upgraded-2-0-0-2-3-2-into-cluster/56014>\
**Category:** Elasticsearch\
**Created:** [July 20, 2016, 7:11pm UTC](https://discuss.elastic.co/t/indexformattoonewexception-after-bringing-node-upgraded-2-0-0-2-3-2-into-cluster/56014 "2016-07-20T19:11:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jthoni](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@jthoni](https://discuss.elastic.co/u/jthoni)\
**Post date:** [July 20, 2016, 7:11pm UTC](https://discuss.elastic.co/t/indexformattoonewexception-after-bringing-node-upgraded-2-0-0-2-3-2-into-cluster/56014/1 "2016-07-20T19:11:07Z")

</div>

This is a rescoping of a question I posted in [Node upgraded 2.0.0 to 2.3.2 can’t communicate with other nodes in cluster](https://discuss.elastic.co/t/node-upgraded-2-0-0-to-2-3-2-cant-communicate-with-other-nodes-in-cluster/55925). I think I have narrowed down the cause, and wanted a clean thread to cover it.

Our cluster is running on ES 2.0.0 (which is on Lucene 5.2.1). When I shut down the node, and bring it back up with ES 2.3.2 (which is on Lucene 5.5.0), the logs on the master get flooded with:

> Caused by: org.apache.lucene.index.IndexFormatTooNewException: Format version is not supported (resource BufferedChecksumIndexInput(SimpleFSIndexInput(path="F:\data\elasticsearch\nodes\0\indices\ml\_v7\2\index\segments\_1ra"))): 6 (needs to be between 0 and 5)

My guess is this is happening because after bringing the node up, I reenable allocation as instructed in step 5 of the [Rolling Upgrades](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html) document, but allocation can't happen between these versions. This seems to be verified in this issue: [Elasticsearch shouldn't try to balance shards from nodes with newer version of lucene to nodes with older versions of lucene](https://github.com/elastic/elasticsearch/issues/4588).

What should the workflow be here? Do I need to upgrade all of my nodes and bring them on line together? Or just keep allocation to 'none' until all nodes are complete?

It is imperative that I don't disrupt the queries on our production site while this is going on, so I want to know what the process should be. 2.0.0 to 2.3.2 is listed as supported for Rolling Upgrade.

thanks,  
~john

---

<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:33pm UTC](https://discuss.elastic.co/t/indexformattoonewexception-after-bringing-node-upgraded-2-0-0-2-3-2-into-cluster/56014/2 "2017-07-05T22:33:57Z")

</div>