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  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
On Thursday, July 24, 2014 6:32:07 PM UTC+2, Manikandan Pounraj wrote:
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
We are getting following exception when elastic search tries to recover
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
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
if this is an issue and that can be fixed in Elastic search.
Issue is causing when* building meta data to get version from
View this message in context:
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 email@example.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.