---
title: Reduce replicas on content data tier
description: Describes what AutoOps detects and surfaces with the Reduce replicas on content data tier insight: Some indices on the content data tier carry more replica shards than your workload needs.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/reduce_replicas_on_content_data_tier
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
---

# Reduce replicas on content data tier
Some indices on the content data tier carry more replica shards than your workload needs. Extra replicas use CPU, memory, and disk on every content node and can slow indexing.
<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     | 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.

### The number of replicas on some indices can be reduced on content nodes


#### What was detected

There was 1 replica detected in content data tier for the following 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 one">
  **Condition**: Shown when replication factor exceeds content tier threshold.Set `number_of_replicas` to 1 for logs-prod-000045 (currently 1 replicas) on the hot 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>


#### Background and impact

Reducing the number of replicas for the content tier can improve performance, save on storage costs, enhance indexing throughput and ensure cluster stability. This is because replicas introduce additional resource usage, which can negatively impact performance and stability.