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

Switch fleet's built-in ILM policies to use .actions.rollover.max_primary_shard_size #99983

Closed
rodrigc opened this issue Sep 27, 2023 · 1 comment · Fixed by #99984
Closed
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management >enhancement Team:Data Management Meta label for data/management team

Comments

@rodrigc
Copy link
Contributor

rodrigc commented Sep 27, 2023

Description

In the Kibana UI, when looking at ILM policies related to fleet, I see warnings:

Maximum index size is deprecated and will be removed in a future version. Use maximum primary shard size instead.

To avoid confusion for the end-user, I recommend that the same changes which were done in elasticsearch's default ILM policies be done for fleet:

Related to:

@rodrigc rodrigc added >enhancement needs:triage Requires assignment of a team area label labels Sep 27, 2023
@gbanasiak gbanasiak added the :Data Management/ILM+SLM Index and Snapshot lifecycle management label Oct 4, 2023
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team and removed needs:triage Requires assignment of a team area label labels Oct 4, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

mattc58 pushed a commit that referenced this issue Oct 7, 2023
…mary_shard_size (#99984)

Fixes #99983

Signed-off-by: Craig Rodrigues <rodrigc@crodrigues.org>
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 >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants