# Recovery failed : IllegalArgumentException\[No enum constant org.apache.lucene.util.Version.4.3.1\] **URL:** \ **Category:** Elasticsearch\ **Created:** [July 24, 2014, 4:31pm UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873 "2014-07-24T16:31:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pounraj\_manikandan](https://avatars.discourse-cdn.com/v4/letter/p/9de0a6/32.png) [@pounraj\_manikandan](https://discuss.elastic.co/u/pounraj_manikandan)\ **Post date:** [July 24, 2014, 4:31pm UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873/1 "2014-07-24T16:31:58Z")
Hello Team, We are using Elastic search for last 2years and we are currently in 0.90.2 release which was upgraded on Jan 2014. For our requirement aggregation (top\_hits) fits and we planned to upgrade to 1.3.0 We are getting following exception when elastic search tries to recover shards. > FYI. This is happening only for a specific index which was created long time. Same index recovered properly with SNAPSHOT version of 1.3.0 (release till JUL 10th. 2014). This is the only index we planned not to reindex which is having 8M docs (40GB) of data even though its too small for elasticsearch. We are also ready for reindexing via our BULK updater. But, it will be good if this is an issue and that can be fixed in Elastic search. Issue is causing when **building meta data to get version from SegmentCommitInfo**. Please suggest. Thanks Pounraj Manikandan ---
**Author:** ![simonw\_3](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@simonw\_3](https://discuss.elastic.co/u/simonw_3)\ **Post date:** [July 28, 2014, 10:58am UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873/2 "2014-07-28T10:58:56Z")
Hey, thanks for raising this. The exception is extremely helpful. This boils down to a bug / inconsistency in Lucene where some of the bugfix releases ie. 3.6.1, 4.3.1, 4.5.1 did specify the minor version in it's version constant where is shouldn't. I just opened [1] that fixes the issue. It's really unfortunate that this problem is really rare and essentially a bug in previous lucene releases. We will fix the issue ASAP and push for 1.3.1 [1] [Support parsing lucene minor version strings by s1monw · Pull Request #7055 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/7055) simon On Thursday, July 24, 2014 6:32:07 PM UTC+2, Manikandan Pounraj wrote: > Hello Team, > > We are using Elastic search for last 2years and we are currently in 0.90.2 > release which was upgraded on Jan 2014. > > For our requirement aggregation (top\_hits) fits and we planned to upgrade > to > 1.3.0 > > We are getting following exception when Elasticsearch tries to recover > shards. > > [recovery\_failure\_no\_enum\_constant\_lucene\_4.3.1 · GitHub](https://gist.github.com/pounrajmanikandan/2e35822827e49bfe490d) > > FYI. This is happening only for a specific index which was created long > time. Same index recovered properly with SNAPSHOT version of 1.3.0 > (release > till JUL 10th. 2014). > > This is the only index we planned not to reindex which is having 8M docs > (40GB) of data even though its too small for elasticsearch. > > We are also ready for reindexing via our BULK updater. But, it will be > good > if this is an issue and that can be fixed in Elastic search. > > Issue is causing when\* building meta data to get version from > SegmentCommitInfo\*. > > Please suggest. > > Thanks > Pounraj Manikandan > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Recovery-failed-IllegalArgumentException-No-enum-constant-org-apache-lucene-util-Version-4-3-1-tp4060560.html](http://elasticsearch-users.115913.n3.nabble.com/Recovery-failed-IllegalArgumentException-No-enum-constant-org-apache-lucene-util-Version-4-3-1-tp4060560.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/aa7108c0-0b2e-482a-9e5d-d8cd31b5fcd6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/aa7108c0-0b2e-482a-9e5d-d8cd31b5fcd6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![pounraj\_manikandan](https://avatars.discourse-cdn.com/v4/letter/p/9de0a6/32.png) [@pounraj\_manikandan](https://discuss.elastic.co/u/pounraj_manikandan)\ **Post date:** [July 28, 2014, 3:17pm UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873/3 "2014-07-28T15:17:34Z")
Thanks Simon. We tested with latest build (1.3.1 SNAPSHOT). **All our old data (0.90.2) got recovered without any issues in 1.3.1.**. Thanks Pounraj Manikandan ---
**Author:** ![simonw\_3](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@simonw\_3](https://discuss.elastic.co/u/simonw_3)\ **Post date:** [July 28, 2014, 3:33pm UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873/4 "2014-07-28T15:33:19Z")
FYI 1.3.1 has been release [http://t.co/rCL9rAofta](http://t.co/rCL9rAofta) go ahead unless you wanna run on 1.3.1-SNAPSHOT thanks for raising this again! simon On Monday, July 28, 2014 5:17:46 PM UTC+2, Manikandan Pounraj wrote: > Thanks Simon. > > We tested with latest build (1.3.1 SNAPSHOT). _All our old data (0.90.2) > got > recovered without any issues in 1.3.1._. > > Thanks > Pounraj Manikandan > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Recovery-failed-IllegalArgumentException-No-enum-constant-org-apache-lucene-util-Version-4-3-1-tp4060560p4060734.html](http://elasticsearch-users.115913.n3.nabble.com/Recovery-failed-IllegalArgumentException-No-enum-constant-org-apache-lucene-util-Version-4-3-1-tp4060560p4060734.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6ff1c816-ad99-4805-86b8-cad3a35e6ac1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6ff1c816-ad99-4805-86b8-cad3a35e6ac1%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![pounraj\_manikandan](https://avatars.discourse-cdn.com/v4/letter/p/9de0a6/32.png) [@pounraj\_manikandan](https://discuss.elastic.co/u/pounraj_manikandan)\ **Post date:** [July 28, 2014, 5:52pm UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873/5 "2014-07-28T17:52:15Z")
This will really help us lot. Thank you. Pounraj Manikandan ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:12am UTC](https://discuss.elastic.co/t/recovery-failed-illegalargumentexception-no-enum-constant-org-apache-lucene-util-version-4-3-1/18873/6 "2017-07-06T01:12:43Z")