# Problems with Snapshot Restore

**URL:** <https://discuss.elastic.co/t/problems-with-snapshot-restore/96921>\
**Category:** Elasticsearch\
**Created:** [August 14, 2017, 7:53am UTC](https://discuss.elastic.co/t/problems-with-snapshot-restore/96921 "2017-08-14T07:53:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![agriffit](https://avatars.discourse-cdn.com/v4/letter/a/b77776/32.png) [@agriffit](https://discuss.elastic.co/u/agriffit)\
**Post date:** [August 14, 2017, 7:53am UTC](https://discuss.elastic.co/t/problems-with-snapshot-restore/96921/1 "2017-08-14T07:53:23Z")

</div>

Hi,

Attempting to restore a snapshot from one cluster into another (same version - 5.0.1).

It seems that all indices that were created using forcemerge are failing to restore. When I do allocation/explain I get

```
  "final_decision" : "NO",
  "final_explanation" : "the shard cannot be assigned because one or more allocation decider returns a 'NO' decision",
  "weight" : 0.6666667,
  "decisions" : [
    {
      "decider" : "filter",
      "decision" : "NO",
      "explanation" : "node does not match index initial recovery filters [null]"
    }

```

Checking the settings on the index I see this initial\_recovery setting, but no idea how to remove it

```
"routing" : {
          "allocation" : {
            "include" : {
              "_id" : ""
            },
            "initial_recovery" : {
              "_id" : "bAqvgAKZSxSheWHG7a9NVg"
            }
          }
        },

```

Anyone seen this before?

Thanks,

Alan

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [August 18, 2017, 8:20pm UTC](https://discuss.elastic.co/t/problems-with-snapshot-restore/96921/2 "2017-08-18T20:20:21Z")

</div>

@agriffit, did you create the snapshot while shrinking the index? You can remove settings on restore using `ignore_index_settings` [parameter](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/modules-snapshots.html#_changing_index_settings_during_restore).

That looks like [this bug](https://github.com/elastic/elasticsearch/pull/24322) that was fixed in 5.4.0.

---

<div class="post-metadata">

**Author:** ![agriffit](https://avatars.discourse-cdn.com/v4/letter/a/b77776/32.png) [@agriffit](https://discuss.elastic.co/u/agriffit)\
**Post date:** [August 21, 2017, 4:15pm UTC](https://discuss.elastic.co/t/problems-with-snapshot-restore/96921/3 "2017-08-21T16:15:28Z")

</div>

Yeh, thanks. ignoring the setting works

```
  "ignore_index_settings": [
    "index.routing.allocation.initial_recovery._id"
  ]

```

The snapshot would have been created after the shrink was complete.

---

<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:** [September 18, 2017, 4:15pm UTC](https://discuss.elastic.co/t/problems-with-snapshot-restore/96921/4 "2017-09-18T16:15:45Z")

</div>

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