# Understanding Index Shard Snapshot Failed Exception

**URL:** <https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572>\
**Category:** Elasticsearch\
**Created:** [December 5, 2018, 4:53pm UTC](https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572 "2018-12-05T16:53:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohail\_kidwai1](https://avatars.discourse-cdn.com/v4/letter/r/46a35a/32.png) [@rohail\_kidwai1](https://discuss.elastic.co/u/rohail_kidwai1)\
**Post date:** [December 5, 2018, 4:53pm UTC](https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572/1 "2018-12-05T16:53:20Z")

</div>

I create snapshots of my indices daily and today I got this error:

> "failures": [  
> {  
> "index": "name-2018.09.05",  
> "index\_uuid": "name-2018.09.05",  
> "shard\_id": 0,  
> "reason": """IndexShardSnapshotFailedException[Failed to get store file metadata]; nested: CorruptIndexException[verification failed : calculated=9w6ma3 stored=1wuvx8p (resource=VerifyingIndexInput(MMapIndexInput(path="PATH/data/nodes/0/indices/xwjuzxurSveAJ6Wpb06MKA/0/index/\_nbd.fdt")))]; """,  
> "node\_id": "ID",  
> "status": "INTERNAL\_SERVER\_ERROR"  
> }

I'm having trouble understanding this. Any help would be appreciated.

I am creating snapshots through elastic curator but I also get this if I do a PUT /\_snapshot/

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [December 5, 2018, 5:08pm UTC](https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572/2 "2018-12-05T17:08:40Z")

</div>

It seems that one of your indices has a corrupted shard:

```auto
CorruptIndexException

```

It drills down deeper to reveal even the path to the corrupt index file:

```auto
path="PATH/data/nodes/0/indices/xwjuzxurSveAJ6Wpb06MKA/0/index/_nbd.fdt"

```

Not sure why it's corrupted, but it's not able to be snapshotted in that state. You _may_ be able to snapshot the non-corrupted shards by setting `partial` to `true` in your Curator config (or with the regular API call).

---

<div class="post-metadata">

**Author:** ![rohail\_kidwai1](https://avatars.discourse-cdn.com/v4/letter/r/46a35a/32.png) [@rohail\_kidwai1](https://discuss.elastic.co/u/rohail_kidwai1)\
**Post date:** [December 5, 2018, 5:14pm UTC](https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572/3 "2018-12-05T17:14:45Z")

</div>

Thanks for responding.

Where can I read more about how to, if possible, fix this shard? A simple google search here wasn't too helpful.

We are creating replicas so can I just delete it?

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [December 5, 2018, 5:45pm UTC](https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572/4 "2018-12-05T17:45:47Z")

</div>

That's a much deeper question. Is it the replica or the primary that is corrupt? If you don't know, then that makes it difficult to know which to address.

I'd ask a new question here in the forums, specifically targeting the shard corruption issue (rather than the snapshot failing) and see if one of the Elasticsearch core developers has a good answer for you.

---

<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:** [January 2, 2019, 5:45pm UTC](https://discuss.elastic.co/t/understanding-index-shard-snapshot-failed-exception/159572/5 "2019-01-02T17:45:49Z")

</div>

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