I know this exception from OOMs, too, when heap got low. You should identify the corrupted shard and make a filesystem copy of it so you do not lose files.
I can not recommend Lucene CheckIndex, because ES uses a modified Lucene 4 index, and may not be able to simply pick up an index "repaired" by Lucene (the "repair" is dropping docs) I have to test if "index.shard.check_on_startup: fix" works at all , it was in the Lucene 3.6 days when it worked quite ok. Since then a lot changed. Jörg -- 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE6nV6y37FbEpaAHSmvBkfrezE1wM9OStJozJZwGL%2BH-Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
