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

ILM UI does not handle max docs and max size properly #31997

Closed
bmcconaghy opened this issue Feb 26, 2019 · 0 comments · Fixed by #31998
Closed

ILM UI does not handle max docs and max size properly #31997

bmcconaghy opened this issue Feb 26, 2019 · 0 comments · Fixed by #31998
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@bmcconaghy
Copy link
Contributor

I have a policy that is showing up in Kibana as
"hot": { "min_age": "0ms", "actions": { "rollover": { "max_age": "30d", "max_docs": 1000000 } }

but it is defined in ES as this:

image

The issue here is twofold: the new default values are kicking in for defined policies (hence the 30 days showing in Kibana), and Kibana only allows for choosing max_size or max_docs, and so last one in wins in the code. Additionally, Kibana does not support mb as a size unit for max size.

@bmcconaghy bmcconaghy added bug Fixes for quality problems that affect the customer experience Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Feb 26, 2019
@bmcconaghy bmcconaghy self-assigned this Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant