# Deleting Corrupt Checksum Files

**URL:** https://discuss.elastic.co/t/deleting-corrupt-checksum-files/22195
**Category:** Elasticsearch
**Created:** [February 16, 2015, 5:53pm UTC](https://discuss.elastic.co/t/deleting-corrupt-checksum-files/22195 "2015-02-16T17:53:03Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Mario\_Rodriguez](https://avatars.discourse-cdn.com/v4/letter/m/e36b37/32.png) [@Mario\_Rodriguez](https://discuss.elastic.co/u/Mario_Rodriguez)
#### Post date: [February 16, 2015, 5:53pm UTC](https://discuss.elastic.co/t/deleting-corrupt-checksum-files/22195/1 "2015-02-16T17:53:03Z")

</div>

I am experiencing a problem with three \_checksum files in 3 different  
shards of one index. We are currently running a 2 node cluster with  
version 1.3.1.

The log on the non-master node cites this as the cause:

_java.io.EOFException: read past EOF:  
MMapIndexInput(path="D:\ElasticSearchData\es\_cluster\_prod\nodes\0\indices\prodcustomer\1\index\_checksums-1418875637019")_

The log on the master node cites this:

_RecoveryEngineException[[prodotterbox][1] Phase[1] Execution failed];  
nested: RecoverFilesRecoveryException[[prodotterbox][1] Failed to transfer  
[0] files with total size of [0b]]; nested: EOFException[read past EOF:  
MMapIndexInput(path="D:\ElasticSearchData\es\_cluster\_prod\nodes\0\indices\prodcustomer\1\index\_checksums-1418875637019")];  
]]_

If the non-master node is shut down, the shards all initialize fine on the  
master node. As soon as I bring up the other node, then I start getting  
these errors logged.

Is it possible and safe to delete the 3 \_checksum files on the master node?

Or would a reindex help resolve this?

Any thoughts?

Thank you!

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c8319de4-5998-4192-83d3-c5c1039d021e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c8319de4-5998-4192-83d3-c5c1039d021e%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Mario\_Rodriguez](https://avatars.discourse-cdn.com/v4/letter/m/e36b37/32.png) [@Mario\_Rodriguez](https://discuss.elastic.co/u/Mario_Rodriguez)
#### Post date: [February 17, 2015, 6:31am UTC](https://discuss.elastic.co/t/deleting-corrupt-checksum-files/22195/2 "2015-02-17T06:31:08Z")

</div>

I ended up deleting the checksum files that were corrupted and the shards  
initialized successfully.

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/42a89455-9605-4277-a986-35c6cd388f40%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/42a89455-9605-4277-a986-35c6cd388f40%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 12:32am UTC](https://discuss.elastic.co/t/deleting-corrupt-checksum-files/22195/3 "2017-07-06T00:32:18Z")

</div>


