Obsolete Zen discovery settings
Legacy Zen Discovery settings remain in cluster configuration even though modern Elasticsearch versions use a different cluster coordination stack. Those keys are ignored at runtime but confuse operators editing settings and can hide the real voting configuration that matters.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Cluster |
| Domains | configuration |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
Legacy Zen Discovery settings (for example discovery.zen.*) are still present in cluster configuration. They are ignored on this Elasticsearch version.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Remove unused zen discovery settings
Condition: Always shown for this insight.
Remove deprecated discovery.zen.* settings from elasticsearch.yml on each affected node. Restart nodes one at a time only after the cluster is green, and wait for each node to rejoin before restarting the next.
Zen Discovery was replaced by the current cluster coordination layer. Settings such as discovery.zen.minimum_master_nodes no longer control master election on supported versions.
Leaving those keys in place does not change runtime behavior, but it misleads operators who read or edit configuration and can distract from the voting configuration that actually matters.
Until obsolete Zen Discovery settings are removed, configuration review stays noisier than it needs to be and unsafe historical values can linger in files and templates.