Archived settingsedit

If you upgrade a cluster with a deprecated persistent cluster setting to a version that no longer supports the setting, Elasticsearch automatically archives that setting. Similarly, if you upgrade a cluster that contains an index with an unsupported index setting, Elasticsearch archives the index setting.

We recommend you remove any archived settings after upgrading. Archived settings are considered invalid and can interfere with your ability to configure other settings.

Archived settings start with the archived. prefix.

Archived cluster settingsedit

Use the following cluster update settings request to check for archived cluster settings. If the request returns an empty object ({ }), there are no archived cluster settings.

GET _cluster/settings?flat_settings=true&filter_path=persistent.archived*

To remove any archived cluster settings, use the following cluster update settings request.

PUT _cluster/settings
  "persistent": {
    "archived.*": null

Elasticsearch doesn’t archive transient cluster settings or settings in elasticsearch.yml. If a node includes an unsupported setting in elasticsearch.yml, it will return an error at startup.

Archived index settingsedit

Before you upgrade, remove any unsupported index settings from index and component templates. Elasticsearch doesn’t archive unsupported index settings in templates during an upgrade. Attempts to use a template that contains an unsupported index setting will fail and return an error. This includes automated operations, such the ILM rollover action.

Archived index settings don’t affect an index’s configuration or most index operations, such as indexing or search. However, you’ll need to remove them before you can configure other settings for the index, such as index.hidden.

Use the following get index settings request to get a list indices with archived settings. If the request returns an empty object ({ }), there are no archived index settings.

GET */_settings?flat_settings=true&filter_path=**.settings.archived*

Removing an index’s archived index settings requires a reindex. Reindexing can be resource-intensive and time-consuming. Before you start, test the reindex with a subset of the data to estimate your time requirements.

POST _reindex
  "source": {
    "index": "my-index"
  "dest": {
    "index": "reindexed-my-index"