# ES - Index/Shard Recovery/ CorruptIndexException - footer mismatch
**URL:** https://discuss.elastic.co/t/es-index-shard-recovery-corruptindexexception-footer-mismatch/20987
**Category:** Elasticsearch
**Created:** [November 29, 2014, 2:47pm UTC](https://discuss.elastic.co/t/es-index-shard-recovery-corruptindexexception-footer-mismatch/20987 "2014-11-29T14:47:28Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Mehmet\_Cem\_Gunturkun](https://discuss.elastic.co/u/Mehmet_Cem_Gunturkun)
#### Post date: [November 29, 2014, 2:47pm UTC](https://discuss.elastic.co/t/es-index-shard-recovery-corruptindexexception-footer-mismatch/20987/1 "2014-11-29T14:47:28Z")
Hey everyone,
I have a problem about shards of nodes. After I restarted ES, it started to
given an exception on recovery for some shards of the a node.
curl -XGET "http:/localhost:9200/\_cat/shards
my\_index 2 p STARTED 7712779 4.2gb ip-1 Motormouth
my\_index 2 r STARTED 7712779 4.2gb ip-2 Harold "Happy" Hogan
my\_index 0 p STARTED 7714351 4.1gb ip-2 Harold "Happy" Hogan
my\_index 0 r UNASSIGNED
my\_index 3 p STARTED 7711363 4.6gb ip-1 Motormouth
my\_index 3 r STARTED 7711363 4.6gb ip-2 Harold "Happy" Hogan
my\_index 1 p STARTED 7712560 4.2gb ip-2 Harold "Happy" Hogan
my\_index 1 r UNASSIGNED
my\_index 4 p STARTED 7714620 2.7gb ip-1 Motormouth
my\_index 4 r STARTED 7714620 2.7gb ip-2 Harold "Happy" Hogan
## It seems that except shards: 0 and 1, all primary shards allocated by "Motormouth". Now I try to allocate replicas for these shards in "Motormouth" but it gives an error likes this:
Corrupted index [corrupted\_3gXTXI3KQtm2e1WPsFntkg] caused by:
CorruptIndexException[codec footer mismatch: actual footer=1308690703 vs
expected footer=-1071082520
--
Do you have any idea?
--
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/6903ba73-6cea-4d9f-ac62-cd513f492588%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6903ba73-6cea-4d9f-ac62-cd513f492588%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)
#### Post date: [October 5, 2016, 2:49pm UTC](https://discuss.elastic.co/t/es-index-shard-recovery-corruptindexexception-footer-mismatch/20987/2 "2016-10-05T14:49:09Z")
Were you able to recover from this scenario?
---
### Author:  [@Mehmet\_Cem\_Gunturkun](https://discuss.elastic.co/u/Mehmet_Cem_Gunturkun)
#### Post date: [October 7, 2016, 4:36pm UTC](https://discuss.elastic.co/t/es-index-shard-recovery-corruptindexexception-footer-mismatch/20987/3 "2016-10-07T16:36:00Z")
I had reindexed whole data, but I think they merged a fix for that situation:
you can check this issue:
>
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:14pm UTC](https://discuss.elastic.co/t/es-index-shard-recovery-corruptindexexception-footer-mismatch/20987/4 "2017-07-05T22:14:01Z")