IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

› › ›

Resume follower API

edit

Resume follower API

edit

This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

Resumes a follower index.

Description

edit

This API resumes a follower index that has been paused either explicitly with the pause follower API or implicitly due to execution that can not be retried due to failure during following. When this API returns, the follower index will resume fetching operations from the leader index.

Request

edit

POST /<follower_index>/_ccr/resume_follow
{
}

Path Parameters

edit

follower_index (required): (string) the name of the follower index

Request Body

edit

max_read_request_operation_count: (integer) the maximum number of operations to pull per read from the remote cluster
max_outstanding_read_requests: (long) the maximum number of outstanding reads requests from the remote cluster
max_read_request_size: (byte value) the maximum size in bytes of per read of a batch of operations pulled from the remote cluster
max_write_request_operation_count: (integer) the maximum number of operations per bulk write request executed on the follower
max_write_request_size: (byte value) the maximum total bytes of operations per bulk write request executed on the follower
max_outstanding_write_requests: (integer) the maximum number of outstanding write requests on the follower
max_write_buffer_count: (integer) the maximum number of operations that can be queued for writing; when this limit is reached, reads from the remote cluster will be deferred until the number of queued operations goes below the limit
max_write_buffer_size: (byte value) the maximum total bytes of operations that can be queued for writing; when this limit is reached, reads from the remote cluster will be deferred until the total bytes of queued operations goes below the limit
max_retry_delay: (time value) the maximum time to wait before retrying an operation that failed exceptionally; an exponential backoff strategy is employed when retrying
read_poll_timeout: (time value) the maximum time to wait for new operations on the remote cluster when the follower index is synchronized with the leader index; when the timeout has elapsed, the poll for operations will return to the follower so that it can update some statistics, and then the follower will immediately attempt to read from the leader again

Authorization

edit

If the Elasticsearch security features are enabled, you must have write and monitor index privileges for the follower index. You must have read and monitor index privileges for the leader index. You must also have manage_ccr cluster privileges on the cluster that contains the follower index. For more information, see Security privileges.

Example

edit

This example resumes a follower index named follower_index:

POST /follower_index/_ccr/resume_follow
{
  "max_read_request_operation_count" : 1024,
  "max_outstanding_read_requests" : 16,
  "max_read_request_size" : "1024k",
  "max_write_request_operation_count" : 32768,
  "max_write_request_size" : "16k",
  "max_outstanding_write_requests" : 8,
  "max_write_buffer_count" : 512,
  "max_write_buffer_size" : "512k",
  "max_retry_delay" : "10s",
  "read_poll_timeout" : "30s"
}

The API returns the following result:

{
  "acknowledged" : true
}

« Pause follower API Unfollow API »