# Warning "Unable to acquire permit to use snapshot files during recovery…" when restarting elasticsearch node

**URL:** <https://discuss.elastic.co/t/warning-unable-to-acquire-permit-to-use-snapshot-files-during-recovery-when-restarting-elasticsearch-node/293543>\
**Category:** Elasticsearch\
**Created:** [January 5, 2022, 1:20pm UTC](https://discuss.elastic.co/t/warning-unable-to-acquire-permit-to-use-snapshot-files-during-recovery-when-restarting-elasticsearch-node/293543 "2022-01-05T13:20:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gregor\_Weckbecker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregor_weckbecker/32/48441_2.png) [@Gregor\_Weckbecker](https://discuss.elastic.co/u/Gregor_Weckbecker)\
**Post date:** [January 5, 2022, 1:20pm UTC](https://discuss.elastic.co/t/warning-unable-to-acquire-permit-to-use-snapshot-files-during-recovery-when-restarting-elasticsearch-node/293543/1 "2022-01-05T13:20:32Z")

</div>

When upgrading our elasticsearch cluster to version 7.16.1, we performing a rolling upgarde as described in the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html). Before the restart we trigger a synced flush and increase `cluster.routing.allocation.node_concurrent_recoveries` to `32`.

After the shard allocation was enabled the node logs multiple multple warings:

> Unable to acquire permit to use snapshot files during recovery, this recovery will recover index files from the source node. Ensure snapshot files can be used during recovery by setting [indices.recovery.max\_concurrent\_snapshot\_file\_downloads] to be no greater than [25]

We did not changed `indices.recovery.max_concurrent_snapshot_file_downloads` from the default (`5`).

What might cause this warning? Is there a known issue when upgrading to 7.16.1?

---

<div class="post-metadata">

**Author:** ![rajim17](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajim17/32/100816_2.png) [@rajim17](https://discuss.elastic.co/u/rajim17)\
**Post date:** [January 25, 2022, 2:35am UTC](https://discuss.elastic.co/t/warning-unable-to-acquire-permit-to-use-snapshot-files-during-recovery-when-restarting-elasticsearch-node/293543/2 "2022-01-25T02:35:35Z")

</div>

After upgrading 7.16.2, we also see above warning. Is it because default(5) is not enough ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 25, 2022, 6:02am UTC](https://discuss.elastic.co/t/warning-unable-to-acquire-permit-to-use-snapshot-files-during-recovery-when-restarting-elasticsearch-node/293543/3 "2022-01-25T06:02:12Z")

</div>

> [@Gregor\_Weckbecker](#):
>
> increase `cluster.routing.allocation.node_concurrent_recoveries` to `32`

That'd explain it. Don't change this setting.

---

<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:** [February 22, 2022, 6:02am UTC](https://discuss.elastic.co/t/warning-unable-to-acquire-permit-to-use-snapshot-files-during-recovery-when-restarting-elasticsearch-node/293543/4 "2022-02-22T06:02:36Z")

</div>

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