Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Designate "system" ILM policies with a dot prefix #51589

Closed
matschaffer opened this issue Jan 29, 2020 · 2 comments
Closed

Designate "system" ILM policies with a dot prefix #51589

matschaffer opened this issue Jan 29, 2020 · 2 comments
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management

Comments

@matschaffer
Copy link
Contributor

Describe the feature:

System indices have the convention of starting with a dot (.). This makes isolation of stack indices from user indices quick and simple.

We don't do the same with ILM policies (or other stack managed resources), for example https://github.com/elastic/elasticsearch/blob/master/x-pack/plugin/core/src/main/resources/watch-history-ilm-policy.json

I'd like to propose that we extend the dot convention to ILM policies or potentially other elasticsearch resources that may contain a mix of both stack and user managed entries.

@cbuescher cbuescher added the :Data Management/ILM+SLM Index and Snapshot lifecycle management label Jan 30, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/ILM+SLM)

@dakrone
Copy link
Member

dakrone commented Feb 12, 2020

We discussed this and decided that we don't want to designate system-provided ILM policies with a dot. Rather, we expect (and encourage) users to change the policies that are put in place by ES (or other tools), and we don't want to confuse the idea of system indices (starting with a dot) that are reserved, since these policies are not reserved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management
Projects
None yet
Development

No branches or pull requests

5 participants