# Translog files corrupted, cluster failing to recover
**URL:** https://discuss.elastic.co/t/translog-files-corrupted-cluster-failing-to-recover/58466
**Category:** Elasticsearch
**Created:** [August 19, 2016, 2:11pm UTC](https://discuss.elastic.co/t/translog-files-corrupted-cluster-failing-to-recover/58466 "2016-08-19T14:11:28Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@tarantin](https://discuss.elastic.co/u/tarantin)
#### Post date: [August 19, 2016, 2:11pm UTC](https://discuss.elastic.co/t/translog-files-corrupted-cluster-failing-to-recover/58466/1 "2016-08-19T14:11:28Z")
After a system crash (disk issues) of a 2 node clusters (shard replication configured to 0), some of the translog tlog files were corrupted/missing in lots of my index. I was wondering if there is a way to recover those indexes event with some tlog file missing ?
In the logs, at the moment, I'm getting the following message when restarting the nodes:
> [2016-08-19 14:06:04,511][WARN][indices.cluster] [Hyperion] [[myindex][3]] marking and sending shard failed due to [failed recovery]
> [myindex][[myindex][3]] IndexShardRecoveryException[failed recovery]; nested: IllegalStateException[translog file doesn't exist with generation: 2 lastCommitted: -1 checkpoint: 8 - translog ids must be consecutive];
> at org.elasticsearch.index.shard.StoreRecoveryService$1.run(StoreRecoveryService.java:179)
> 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:745)
> Caused by: java.lang.IllegalStateException: translog file doesn't exist with generation: 2 lastCommitted: -1 checkpoint: 8 - translog ids must be consecutive
> at org.elasticsearch.index.translog.Translog.recoverFromFiles(Translog.java:328)
> at org.elasticsearch.index.translog.Translog.(Translog.java:179)
> at org.elasticsearch.index.engine.InternalEngine.openTranslog(InternalEngine.java:208)
> at org.elasticsearch.index.engine.InternalEngine.(InternalEngine.java:151)
> at org.elasticsearch.index.engine.InternalEngineFactory.newReadWriteEngine(InternalEngineFactory.java:25)
> at org.elasticsearch.index.shard.IndexShard.newEngine(IndexShard.java:1509)
> at org.elasticsearch.index.shard.IndexShard.createNewEngine(IndexShard.java:1493)
> at org.elasticsearch.index.shard.IndexShard.internalPerformTranslogRecovery(IndexShard.java:966)
> at org.elasticsearch.index.shard.IndexShard.performTranslogRecovery(IndexShard.java:938)
> at org.elasticsearch.index.shard.StoreRecoveryService.recoverFromStore(StoreRecoveryService.java:241)
> at org.elasticsearch.index.shard.StoreRecoveryService.access$100(StoreRecoveryService.java:56)
> at org.elasticsearch.index.shard.StoreRecoveryService$1.run(StoreRecoveryService.java:129)
> ... 3 more
The problem occured on Elasticsearch 2.1 and I tried to solve the problem by migrating to 2.3.5 but it didn't solve the problem.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [August 20, 2016, 7:26am UTC](https://discuss.elastic.co/t/translog-files-corrupted-cluster-failing-to-recover/58466/2 "2016-08-20T07:26:25Z")
> [@tarantin](#):
>
> I was wondering if there is a way to recover those indexes event with some tlog file missing
Bad translogs are not really a version specific issue. You can either process the original data again, or accept that this data is lost ☹
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:26pm UTC](https://discuss.elastic.co/t/translog-files-corrupted-cluster-failing-to-recover/58466/3 "2017-07-05T22:26:29Z")