Recovery failed : IllegalArgumentException[No enum constant org.apache.lucene.util.Version.4.3.1]

pounraj_manikandan · July 24, 2014, 4:31pm

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.

gist.github.com

https://gist.github.com/pounrajmanikandan/2e35822827e49bfe490d

recovery_failure_no_enum_constant_lucene_4.3.1

[2014-07-24 02:15:37,198][WARN ][index.engine.internal    ] [es_f1_01] [vs_signupaudit_copy][3] failed engine [corrupted preexisting index]
[2014-07-24 02:15:37,199][WARN ][indices.cluster          ] [es_f1_01] [vs_signupaudit_copy][3] failed to start shard
java.lang.IllegalArgumentException: No enum constant org.apache.lucene.util.Version.4.3.1
        at java.lang.Enum.valueOf(Enum.java:236)
        at org.apache.lucene.util.Version.valueOf(Version.java:32)
        at org.apache.lucene.util.Version.parseLeniently(Version.java:250)
        at org.elasticsearch.index.store.Store$MetadataSnapshot.buildMetadata(Store.java:451)
        at org.elasticsearch.index.store.Store$MetadataSnapshot.<init>(Store.java:433)
        at org.elasticsearch.index.store.Store.getMetadata(Store.java:144)
        at org.elasticsearch.indices.cluster.IndicesClusterStateService.applyInitializingShard(IndicesClusterStateService.java:724)

This file has been truncated. show original

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

simonw_3 · July 28, 2014, 10:58am

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

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

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
Sent from the Elasticsearch Users mailing list archive at 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/aa7108c0-0b2e-482a-9e5d-d8cd31b5fcd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

pounraj_manikandan · July 28, 2014, 3:17pm

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

simonw_3 · July 28, 2014, 3:33pm

FYI 1.3.1 has been release 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
Sent from the Elasticsearch Users mailing list archive at 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6ff1c816-ad99-4805-86b8-cad3a35e6ac1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

pounraj_manikandan · July 28, 2014, 5:52pm

This will really help us lot. Thank you.

Pounraj Manikandan