# TranslogCorruptedException
**URL:** https://community.cratedb.com/t/translogcorruptedexception/1264
**Category:** CrateDB
**Created:** [October 25, 2022, 7:28am UTC](https://community.cratedb.com/t/translogcorruptedexception/1264 "2022-10-25T07:28:09Z")
**Posts on this page:** 1
**Showing post:** 7
### Author:  [@smu](https://community.cratedb.com/u/smu)
#### Post date: [September 3, 2024, 7:50am UTC](https://community.cratedb.com/t/translogcorruptedexception/1264/7 "2024-09-03T07:50:36Z")
Unfortunately for this situation, we moved away from using ES as a fork since CrateDB 4.0.0 (we integrated required parts into our code base). Thus, using any ES code independent isn’t working anymore. You could try to include all CrateDB and Lucene JAR files located at `/lib` into the class path of the `elasticsearch-cli` script which the `elasticsearch-shard` tool is using (see [elasticsearch/distribution/src/bin/elasticsearch-shard at v8.12.2 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/blob/v8.12.2/distribution/src/bin/elasticsearch-shard) and [elasticsearch/distribution/src/bin/elasticsearch-cli at v8.12.2 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/blob/v8.12.2/distribution/src/bin/elasticsearch-cli).
This would load the required lucene libraries.
Also ensure that you are invoking it with the same Java version the related CrateDB version uses. For CrateDB 5.6.5 use Java 21, see [crate/pom.xml at 5.6.5 · crate/crate · GitHub](https://github.com/crate/crate/blob/5.6.5/pom.xml#L239).
Another solution would be (that’s what the `elasticsearch-shard` CLI is actually doing) to remove the files which are corrupted manually while the CrateDB instance isn’t running.
Of course both ways will result in a data loss.
---
_[View the full topic](https://community.cratedb.com/t/translogcorruptedexception/1264)._