# Restore are 20x slower after migrating from 5.x to 7.x

**URL:** <https://discuss.elastic.co/t/restore-are-20x-slower-after-migrating-from-5-x-to-7-x/312281>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [August 17, 2022, 12:18pm UTC](https://discuss.elastic.co/t/restore-are-20x-slower-after-migrating-from-5-x-to-7-x/312281 "2022-08-17T12:18:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bqk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bqk/32/109775_2.png) [@bqk](https://discuss.elastic.co/u/bqk)\
**Post date:** [August 17, 2022, 12:18pm UTC](https://discuss.elastic.co/t/restore-are-20x-slower-after-migrating-from-5-x-to-7-x/312281/1 "2022-08-17T12:18:41Z")

</div>

Hi,  
Found some related topics but no actual answer.  
We run daily snapshots in production, and every morning we wipe our test cluster and do a full restore. This way we test our backups and our staff has playground environment with very good data.

This worked fine with 5.x, took a bit less than an hour to complete, acceptable. However since switching to 7.x, it does not even complete in a day.

An empty index took 9.2m to recover, according to \_cat/recovery, most of the empty ones took around that time.

I have tried fiddling with the settings:

```auto
"cluster": {
      "routing": {
        "allocation": {
          "node_concurrent_recoveries": "10",
          "node_initial_primaries_recoveries": "20"
        }
      }
    },
    "indices": {
      "recovery": {
        "max_bytes_per_sec": "250mb",
        "max_concurrent_file_chunks": "5"
      }
    }

```

But that does not change anything to the speed.  
Is there anyway to get back to decent speed for recovery or is our use case not something supported anymore?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 22, 2022, 12:41am UTC](https://discuss.elastic.co/t/restore-are-20x-slower-after-migrating-from-5-x-to-7-x/312281/2 "2022-08-22T00:41:12Z")

</div>

Welcome to our community! 😃

Can you check hot threads when you are restoring?  
Also the output from [Restore a snapshot | Elasticsearch Guide [8.3] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-restore-snapshot.html#monitor-restore) when you are restoring?

---

<div class="post-metadata">

**Author:** ![bqk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bqk/32/109775_2.png) [@bqk](https://discuss.elastic.co/u/bqk)\
**Post date:** [August 24, 2022, 10:16am UTC](https://discuss.elastic.co/t/restore-are-20x-slower-after-migrating-from-5-x-to-7-x/312281/3 "2022-08-24T10:16:17Z")

</div>

It ended up taking 5 days for 50Gb.  
I cannot really take down the cluster anymore due to that problem preventing anyone from working in that case.

I tried deleting a single index and restoring it but I get an error:

```auto
unknown field name [min_version]

```

even though both source and target are at the exact same version, 7.17.5

---

<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 21, 2022, 10:16am UTC](https://discuss.elastic.co/t/restore-are-20x-slower-after-migrating-from-5-x-to-7-x/312281/4 "2022-09-21T10:16:23Z")

</div>

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