﻿---
title: Cross-cluster replication settings
description: These cross-cluster replication settings can be dynamically updated on a live cluster with the cluster update settings API. The following setting can...
url: https://www.elastic.co/elastic/docs-builder/docs/2773/reference/elasticsearch/configuration-reference/cross-cluster-replication-settings
products:
  - Elasticsearch
applies_to:
  - Self-managed Elastic deployments: Generally available
---

# Cross-cluster replication settings
These cross-cluster replication settings can be dynamically updated on a live cluster with the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings).

## Remote recovery settings

The following setting can be used to rate-limit the data transmitted during [remote recoveries](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/2773/deploy-manage/tools/cross-cluster-replication#ccr-remote-recovery):
<definitions>
  <definition term="ccr.indices.recovery.max_bytes_per_sec (Dynamic)">
    Limits the total inbound and outbound remote recovery traffic on each node. Since this limit applies on each node, but there may be many nodes performing remote recoveries concurrently, the total amount of remote recovery bytes may be much higher than this limit. If you set this limit too high then there is a risk that ongoing remote recoveries will consume an excess of bandwidth (or other resources) which could destabilize the cluster. This setting is used by both the leader and follower clusters. For example if it is set to `20mb` on a leader, the leader will only send `20mb/s` to the follower even if the follower is requesting and can accept `60mb/s`. Defaults to `40mb`.
  </definition>
</definitions>


## Advanced remote recovery settings

The following *expert* settings can be set to manage the resources consumed by remote recoveries:
<definitions>
  <definition term="ccr.indices.recovery.max_concurrent_file_chunks (Dynamic)">
    Controls the number of file chunk requests that can be sent in parallel per recovery. As multiple remote recoveries might already running in parallel, increasing this expert-level setting might only help in situations where remote recovery of a single shard is not reaching the total inbound and outbound remote recovery traffic as configured by `ccr.indices.recovery.max_bytes_per_sec`. Defaults to `5`. The maximum allowed value is `10`.
  </definition>
  <definition term="ccr.indices.recovery.chunk_size(Dynamic)">
    Controls the chunk size requested by the follower during file transfer. Defaults to `1mb`.
  </definition>
  <definition term="ccr.indices.recovery.recovery_activity_timeout(Dynamic)">
    Controls the timeout for recovery activity. This timeout primarily applies on the leader cluster. The leader cluster must open resources in-memory to supply data to the follower during the recovery process. If the leader does not receive recovery requests from the follower for this period of time, it will close the resources. Defaults to 60 seconds.
  </definition>
  <definition term="ccr.indices.recovery.internal_action_timeout (Dynamic)">
    Controls the timeout for individual network requests during the remote recovery process. An individual action timing out can fail the recovery. Defaults to 60 seconds.
  </definition>
</definitions>