# Deleted alias still causing conflict when restoring snapshot

**URL:** <https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637>\
**Category:** Elasticsearch\
**Created:** [November 27, 2019, 9:14am UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637 "2019-11-27T09:14:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![V.krae](https://avatars.discourse-cdn.com/v4/letter/v/e19b73/32.png) [@V.krae](https://discuss.elastic.co/u/V.krae)\
**Post date:** [November 27, 2019, 9:14am UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637/1 "2019-11-27T09:14:58Z")

</div>

Hi everyone,

I want to restore an indice from a snapshot with a certain name. It turned out that the same name was set as an alias for another index. So I deleted the alias, because I did not need it anymore.

Now, if I call

` GET /_all/_alias`

it does not list the alias anymore. But if I call \_restore on my snapshot I still get a conflict message caused by the alias.

Does someone know what might be the problem here?

I am using Elasticsearch 7.4 and I am running the commands via Kibana Console.

---

<div class="post-metadata">

**Author:** ![V.krae](https://avatars.discourse-cdn.com/v4/letter/v/e19b73/32.png) [@V.krae](https://discuss.elastic.co/u/V.krae)\
**Post date:** [November 27, 2019, 10:05am UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637/2 "2019-11-27T10:05:53Z")

</div>

I figured out that the alias must be deleted in the snapshot too. So saving a new snapshot without alias worked for me.

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [November 27, 2019, 12:26pm UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637/3 "2019-11-27T12:26:54Z")

</div>

Hi @V.krae

This sounds like a potential bug to me. Were you unable to restore a snapshot that contained a certain alias even though you did not have an index or alias by that same name in your cluster?  
I'm assuming you didn't as you said that you deleted the alias?

---

<div class="post-metadata">

**Author:** ![V.krae](https://avatars.discourse-cdn.com/v4/letter/v/e19b73/32.png) [@V.krae](https://discuss.elastic.co/u/V.krae)\
**Post date:** [November 28, 2019, 10:52am UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637/4 "2019-11-28T10:52:41Z")

</div>

Hi,

yes I was unable to restore the snapshot eventhough I deleted everything with the same name and alias in my cluster.

But in the snapshot the index I wanted rename while restoring still had the same name as alias stored. I guess that caused the conflict since the index name was already included as alias.

So the name of the index would have been identical to the alias after restoring. I guess it does make sense that this case is causing a conflict.

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [November 28, 2019, 10:59am UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637/5 "2019-11-28T10:59:19Z")

</div>

Right, thanks for getting back to me and clarifying @V.krae 🙂

---

<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:** [December 26, 2019, 10:59am UTC](https://discuss.elastic.co/t/deleted-alias-still-causing-conflict-when-restoring-snapshot/209637/6 "2019-12-26T10:59:24Z")

</div>

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