Non-assignment and restoration of fragments after intensive updating

Question

The shard will not recover after an intensive update. What can I do?

Is it a matter of waiting for a fragment to recover? I see this over and over on a damaged node, which is apparently a master:

[IndexShardGatewayRecoveryException[[global][2] failed to recover shard]; nested:
ElasticsearchIllegalArgumentException[No version type match [6]]; ]]
[2014-06-06 12:32:43,249][WARN ][indices.cluster] [Centurion] [global][5] failed to start shard
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: [global][5] failed to recover shard
    at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:241)
    at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:132)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.ElasticsearchIllegalArgumentException: No version type match [51]
    at org.elasticsearch.index.VersionType.fromValue(VersionType.java:307)
    at org.elasticsearch.index.translog.Translog$Index.readFrom(Translog.java:506)
    at org.elasticsearch.index.translog.TranslogStreams.readTranslogOperation(TranslogStreams.java:52)
    at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:218)
    ... 4 more

Answer 1

Judging by the org.elasticsearch.index.translogstack trace, it looks like a damaged transaction log that could have occurred if the process crashed while trying to flush its updates to disk. I saw this from time to time when posting Elasticsearch in Bonsai.io .

indexog, , , .

, .

API , , GC. . node ​​ node.