# Elasticsearch - Curator -Rollover+Aliasing - Is it expected? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 26, 2018, 12:55am UTC](https://discuss.elastic.co/t/elasticsearch-curator-rollover-aliasing-is-it-expected/137329 "2018-06-26T00:55:37Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\ **Post date:** [June 26, 2018, 12:55am UTC](https://discuss.elastic.co/t/elasticsearch-curator-rollover-aliasing-is-it-expected/137329/1 "2018-06-26T00:55:37Z")
Hi I'm using curator 5.5 for rollover. When I try to rollover on alias, it does rollover based on condition. To add additional alias to the new indice due to rollover, I used extra\_settings. Though the new indice is associated to the alias as in extra settings, it removes the alias from exisiting indice. Why? Ex. Let us say I have indice named i-000001 with aliases "active", and "all". If I rollover on active (USING CURATOR), it rollover nicely to i-000002, and associates alias "all" to it. But "all" is removed from i-000001. Shouldn't both i-000001 and i-000002 has the alias "all". The intent it to have new indice also be part of the alias. I have to use explict "alias" action now to resolve it. But, it would unnecessarily get all indices if I have multiple rollovers done with. Any suggestions (or) it is a known behavior of curator ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [June 27, 2018, 2:55am UTC](https://discuss.elastic.co/t/elasticsearch-curator-rollover-aliasing-is-it-expected/137329/2 "2018-06-27T02:55:21Z")
This is the expected behavior of Rollover API. The alias will always point to the latest index. Rollover API can never be aware that there is an alias (named `all`) with a special rule in which needs to be treated differently. So any alias will be treated as a regular alias and that means that will always point to the latest index. ---
**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\ **Post date:** [June 27, 2018, 9:46pm UTC](https://discuss.elastic.co/t/elasticsearch-curator-rollover-aliasing-is-it-expected/137329/3 "2018-06-27T21:46:40Z")
Hi Thiago, Agreed that RolloverAPI should rollover the alias that is used for rolling over. But the issue here is around the alias in extra\_settings of the curator config. This is not the alias that is rolled-over rather an additional alias that needs to be added to new indice that is created because of rollover action. ---
**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:** [June 29, 2018, 8:50pm UTC](https://discuss.elastic.co/t/elasticsearch-curator-rollover-aliasing-is-it-expected/137329/4 "2018-06-29T20:50:33Z")
> [@Karthik\_Ramachandran](#): > > Any suggestions (or) it is a known behavior of curator This is not Curator, but the Elasticsearch API at work here. Curator only passes the `extra_settings` to the Rollover API call. If any alias oddity is going on, it's something that Elasticsearch is doing, not Curator. With that said, I do not know why this might be _removing_ an established alias. What do you actually have in your `extra_settings` block? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 27, 2018, 8:50pm UTC](https://discuss.elastic.co/t/elasticsearch-curator-rollover-aliasing-is-it-expected/137329/5 "2018-07-27T20:50:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.