---
title: High replica count on cold nodes
description: Describes what AutoOps detects and surfaces with the High replica count on cold nodes insight: Some indices on cold nodes have a higher replica count than the threshold for their recovery model.
url: https://www.elastic.co/docs/reference/autoops-insights/elasticsearch/high_replica_count_on_cold_nodes
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
---

# High replica count on cold nodes
Some indices on cold nodes have a higher replica count than the threshold for their recovery model. Reducing replicas to zero is only safe when the index is fully mounted from a searchable snapshot; other cold indices need a live replica or a fully mounted searchable snapshot to stay recoverable.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://www.elastic.co/docs/reference/autoops-insights/elasticsearch).
</note>


## Insight details


| Field     | Value                             |
|-----------|-----------------------------------|
| Component | Elasticsearch                     |
| Severity  | Low                               |
| Scope     | Node                              |
| Domains   | replication, resource-utilization |


## 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.

### High replica count on some indices on cold nodes


#### What was detected

2 replicas on cold nodes for these indices: `logs-prod-000045`, `logs-prod-000046`.

#### Recommendations

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

<dropdown title="Reduce replicas to zero">
  **Condition**: Shown when affected cold index is fully mounted from a searchable snapshot (restored-* naming) and replication factor exceeds the fully mounted cold threshold (0).Confirm logs-prod-000045 is backed up, then set `number_of_replicas` to 0 on the cold tier with the action below (currently 2 replicas). Fewer replicas can increase search latency because fewer nodes serve reads.
  ```json

  {
    "index": {
      "number_of_replicas": 0
    }
  }
  ```

  <note>
    Requires the `manage` index privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
  </note>
</dropdown>

<dropdown title="Reduce replicas to one">
  **Condition**: Shown when affected cold index is not fully mounted from a searchable snapshot and number_of_replicas is greater than 1.Set `number_of_replicas` to 1 for logs-prod-000045 (currently 2 replicas) on the cold tier with the action below. Fewer replicas can increase search latency because fewer nodes serve reads.
  ```json

  {
    "index": {
      "number_of_replicas": 1
    }
  }
  ```

  <note>
    Requires the `manage` index privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
  </note>
</dropdown>

<dropdown title="Set up fully mounted searchable snapshots">
  **Condition**: Shown when affected cold index is not fully mounted from a searchable snapshot.Move this index to a fully mounted searchable snapshot in your ILM policy for the cold phase. See [Searchable snapshot](https://docs-demo.elastic.dev/docs/reference/elasticsearch/index-lifecycle-actions/ilm-searchable-snapshot). Fully mounted indices recover from the underlying snapshot, so you can safely run them with zero replicas without losing availability if a node fails.
</dropdown>


#### Background and impact

Each replica is a full copy of a primary shard. Higher replica counts improve availability and search capacity, but they also multiply disk use and write amplification: every index, update, and recovery must reach every replica.
On the cold tier, reducing replicas lowers cost for data that is accessed less often. That tradeoff is safe at zero replicas only when the index is fully mounted from a searchable snapshot, because Elasticsearch can recover the index from the snapshot if a node is lost. If a cold index is not fully mounted and its replicas are removed, losing a node can leave the index unavailable until recovery completes, and searches that need the missing shard can fail.

## Guide

[Increase tier capacity](https://docs-demo.elastic.dev/docs/troubleshoot/elasticsearch/increase-tier-capacity)