Corrupted Index

Dear all,

We are using ES-1.3.7 for our search Application. Sometime back we upgraded
from 0.90.5 to 1.3.7. We have 2 master nodes and 3 data nodes. We are
getting CorruptedIndexException when Shard initialization is happening.
This is the second time we are facing such issue since last update. Last
time, only one shard got corrupted, but now almost 15 to 20 shards got
corrupted. Each shard has only ~500MB data.

log trace :

[2015-04-19 22:49:57,552][WARN ][cluster.action.shard ] [Node1]

[138][3] received shard failed for [138][3], node[EkvXNBUOTcuEfWo4SG72bA],
[P], s[INITIALIZING], indexUUID [na], reason [Failed to start shard,
message [IndexShardGatewayRecoveryException[[138][3] failed to fetch index
version after copying it over]; nested: CorruptIndexException[[138][3]
Corrupted index [corrupted_gb9JvBzdRQKqkhEeaXFEIA] caused by:
CorruptIndexException[checksum failed (hardware problem?) : expected=637c1x
resource=($FSIndexOutput@54916f2a)]]; ]]

[2015-04-19 22:49:57,626][WARN ][cluster.action.shard ] [Node1]

[138][3] received shard failed for [138][3], node[Q1eAQgNtSJ2BLlMevzRzcA],
[P], s[INITIALIZING], indexUUID [na], reason [Failed to start shard,
message [IndexShardGatewayRecoveryException[[138][3] failed recovery];
nested: EngineCreationFailureException[[138][3] failed to open reader on
writer]; nested: FileNotFoundException[No such file [_1gy_x.del]]; ]]

Thanks in advance

Ranjith Venkatesan

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
To view this discussion on the web visit
For more options, visit