Shard corruption

We have several ES clusters running 1.0.0. It appears that there is a
shard corruption on a couple of clusters. It reports NPE for one of the
shard and it appears documents are not getting indexed on the shard from
then on.

[2014-04-24T15:10:12.181+0000][DEBUG][action.bulk ] [prod-
search-42] [main.5.2][81] failed to execute bulk item (index) index {[main.
5.2][Attachment][......-1452300182662303400-WNFL11.xlsx-1], source[{"guid":

at org.elasticsearch.common.lucene.uid.Versions.loadDocIdAndVersion(
at org.elasticsearch.common.lucene.uid.Versions.loadDocIdAndVersion(
at org.elasticsearch.common.lucene.uid.Versions.loadVersion(Versions
at org.elasticsearch.index.engine.internal.InternalEngine.
at org.elasticsearch.index.engine.internal.InternalEngine.innerIndex
at org.elasticsearch.index.engine.internal.InternalEngine.index(
at org.elasticsearch.index.shard.service.InternalIndexShard.index(
at org.elasticsearch.action.bulk.TransportShardBulkAction.
at org.elasticsearch.action.bulk.TransportShardBulkAction.
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

At this point it appears shard 81 is corrupt, and it'll report bulk index
error for all the new index request on this shard. I have the same concern
as the previous poster who reported shard failure that this is a critical
error but it's logged as DEBUG. What can we do at this point, short of
rebuilding the indices? Is there anything we can do to prevent this
problem from happening in the future?

Jongyoon Lee

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