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

Provide index level indication when index.codec is set at the node level #26130

Closed
ppf2 opened this issue Aug 9, 2017 · 0 comments
Closed

Provide index level indication when index.codec is set at the node level #26130

ppf2 opened this issue Aug 9, 2017 · 0 comments
Labels

Comments

@ppf2
Copy link
Member

@ppf2 ppf2 commented Aug 9, 2017

https://www.elastic.co/guide/en/elasticsearch/reference/5.0/breaking_50_settings_changes.html#_index_level_settings

Starting in 5.0, most index level settings cannot be set at the node level anymore, except for a few like index.codec.

The user experience of applying this at the node level can be improved. For example, say an admin added index.codec: best_compression to the node configurations but don't remember when this was added. What this means is the new indices created after index.codec is added should be using best compression. But there isn't a good way for admins to tell because if they do a GET _settings against an index that is created after the node is started with index.codec, the index settings will not show that the index has index.codec configured. They can only tell that index.codec is set from the nodes info api (but that's at the node level).

It will be helpful we can apply index.codec to the index settings for indices that are created while the nodes have index.codec set (and if it shows something different, then it will just imply that the index settings have been updated via a direct index settings call post index creation). Or provide some indication from the segments api to show if the stored fields are compressed (using best compression)?

@ppf2 ppf2 added the >enhancement label Aug 9, 2017
jpountz added a commit to jpountz/elasticsearch that referenced this issue Aug 10, 2017
This contains information about whether high compression was enabled for instance.

Closes elastic#26130
jpountz added a commit that referenced this issue Aug 16, 2017
This contains information about whether high compression was enabled for instance.

Closes #26130
jpountz added a commit that referenced this issue Aug 16, 2017
This contains information about whether high compression was enabled for instance.

Closes #26130
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.