OpenSearch/docs/reference/ccr/apis/follow-request-body.asciidoc

44 lines
1.8 KiB
Plaintext
Raw Normal View History

`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-units,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-units,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-units,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-units,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-units,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