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

Prevent index level setting from being configured on a node level #17144

Merged
merged 1 commit into from Mar 17, 2016

Commits on Mar 17, 2016

  1. Prevent index level setting from being configured on a node level

    Today we allow to set all kinds of index level settings on the node level which
    is error prone and difficult to get right in a consistent manner.
    For instance if some analyzers are setup in a yaml config file some nodes might
    not have these analyzers and then index creation fails.
    
    Nevertheless, this change allows some selected settings to be specified on a node level
    for instance:
     * `index.codec` which is used in a hot/cold node architecture and it's value is really per node or per index
     * `index.store.fs.fs_lock` which is also dependent on the filesystem a node uses
    
    All other index level setting must be specified on the index level. For existing clusters the index must be closed
    and all settings must be updated via the API on each of the indices.
    
    Closes elastic#16799
    s1monw committed Mar 17, 2016
    Copy the full SHA
    e91a141 View commit details
    Browse the repository at this point in the history