# Recovery From Missing translog.ckp files with 2.0 Upgrade

**URL:** <https://discuss.elastic.co/t/recovery-from-missing-translog-ckp-files-with-2-0-upgrade/33694>\
**Category:** Elasticsearch\
**Created:** [November 4, 2015, 1:46am UTC](https://discuss.elastic.co/t/recovery-from-missing-translog-ckp-files-with-2-0-upgrade/33694 "2015-11-04T01:46:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulr](https://avatars.discourse-cdn.com/v4/letter/p/c4cdca/32.png) [@paulr](https://discuss.elastic.co/u/paulr)\
**Post date:** [November 4, 2015, 1:46am UTC](https://discuss.elastic.co/t/recovery-from-missing-translog-ckp-files-with-2-0-upgrade/33694/1 "2015-11-04T01:46:10Z")

</div>

I've run an errant command, and accidentally deleted all `*/translog/translog.ckp` files for my single-node cluster. This occurred during the upgrade process from ES 1.7.3 to ES 2.0.0.

I managed to keep a backup of the actual `*.tlog` files for all indices, but I don't have a copy of the checkpoint files.

I'm OK with a small amount of dataloss in each index; the alternative seems to be full loss of all of my indices. **Is there a way to disable checking the translogs entirely, in order to trigger a recovery attempt**? This isn't production, but I'd like to make sure if something similar goes wrong on our production cluster there would be a way to recover.

Any help appreciated.

Cheers,  
Paul

---

<div class="post-metadata">

**Author:** ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)\
**Post date:** [November 20, 2015, 1:25am UTC](https://discuss.elastic.co/t/recovery-from-missing-translog-ckp-files-with-2-0-upgrade/33694/2 "2015-11-20T01:25:28Z")

</div>

A hard crash caused a couple of my indices' translogs to be corrupted. For one index, I was able to remove the translog dir on one node and re-open the index to recover. On the other index, no combination of removing the translog dir on the data nodes helped me recover the index. Sometimes would get a NoSuchFileException, others a FileAlreadyExistsException.

That doesn't help you, Paul, but I'm hoping someone can chime in and confirm what can or can't be done when elasticsearch is unhappy with the translogs.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:37pm UTC](https://discuss.elastic.co/t/recovery-from-missing-translog-ckp-files-with-2-0-upgrade/33694/3 "2017-07-05T23:37:06Z")

</div>