# Corrupted index after the amazon network issue

**URL:** <https://discuss.elastic.co/t/corrupted-index-after-the-amazon-network-issue/74607>\
**Category:** Elasticsearch\
**Created:** [February 10, 2017, 6:23am UTC](https://discuss.elastic.co/t/corrupted-index-after-the-amazon-network-issue/74607 "2017-02-10T06:23:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balamurugan](https://avatars.discourse-cdn.com/v4/letter/b/5daacb/32.png) [@Balamurugan](https://discuss.elastic.co/u/Balamurugan)\
**Post date:** [February 10, 2017, 6:23am UTC](https://discuss.elastic.co/t/corrupted-index-after-the-amazon-network-issue/74607/1 "2017-02-10T06:23:24Z")

</div>

Hi Team,

We had a 3 node ES cluster and that has been hosted on AWS . We can see below error message, after the amazon network connectivity issue( see [https://status.aws.amazon.com/](https://status.aws.amazon.com/)) which is happen on today. Could you please advise how I can bring up the cluster again to good state, without any data?

[index.store] [[.marvel-2015.03.19][0] Failed to open / find files while reading metadata snapshot  
[2017-02-10 01:54:54,379][WARN][index.engine.internal] [.marvel-2015.03.16][0] failed engine [corrupted preexisting index]  
org.apache.lucene.index.CorruptIndexException: [.marvel-2015.03.16][0] Preexisting corrupted index [corrupted\_Jja1GRiPTFyzm4G\_tuEvsg] caused by: CorruptIndexException[codec footer mismatch: actua  
l footer=1431655765 vs expected footer=-1071082520 (resource: NIOFSIndexInput(path="/es-data/prod-evs01/nodes/0/indices/.marvel-2015.03.16/0/index/\_83k\_es090\_0.doc"))]

One file was corrupted under the /nodes/0/indices/.marvel-2015.03.16/0/index/\_83k\_es090\_0.doc .please let me know how to recover this file or how i can delete this file and reindex again ??

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [February 10, 2017, 9:55am UTC](https://discuss.elastic.co/t/corrupted-index-after-the-amazon-network-issue/74607/2 "2017-02-10T09:55:40Z")

</div>

You can either delete the `.marvel-2015.03.16` index (and lose the corresponding data) or restore it again from a snapshot if you've done regular backups.

---

<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:** [March 10, 2017, 9:55am UTC](https://discuss.elastic.co/t/corrupted-index-after-the-amazon-network-issue/74607/3 "2017-03-10T09:55:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.