---
title: Zen Discovery Settings Not Used
description: Describes what AutoOps detects and surfaces with the Zen Discovery Settings Not Used insight: Legacy Zen Discovery settings remain in cluster configuration even though modern Elasticsearch versions use a different cluster coordination stack.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/zen_discovery_settings_not_used
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Zen Discovery Settings Not Used
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 quorum and voting configuration that matters.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value         |
|-----------|---------------|
| Component | Elasticsearch |
| Severity  | Low           |
| Scope     | Cluster       |
| Domains   | configuration |


## Example: What you might see in AutoOps

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.

### Zen Discovery settings are configured but not used


#### What was detected

_No description available._

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="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.
</dropdown>


#### Background and impact

Impact: Zen discovery was replaced and is not relevant for the cluster current version and above. This might be misleading when reading and editing configurations.
Up until version 6 it was possible to inadvertently set unsafe settings with the Zen Discovery mechanism. The setting was deprecated and is now redundant, so it should be removed to avoid confusion.