68d07fc01f
We already archive index level settings if we find an unknown or invalid/broken value for a setting on node startup. The same could potentially happen for persistent cluster level settings if we remove a setting or if we add validation to a setting that didn't exist in the past. To ensure that only valid settings are recovered into the cluster state we archive them (prefix them with `archive.` and log a warning. Tools that check the cluster settings can then warn users that they have broken settings in their clusterstate that got archived. |
||
|---|---|---|
| .. | ||
| src/main | ||
| build.gradle | ||
| version.properties | ||