104 lines
3.4 KiB
Plaintext
104 lines
3.4 KiB
Plaintext
[role="xpack"]
|
|
[testenv="platinum"]
|
|
`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
|
|
|
|
===== Default values
|
|
|
|
//////////////////////////
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
PUT /follower_index/_ccr/follow?wait_for_active_shards=1
|
|
{
|
|
"remote_cluster" : "remote_cluster",
|
|
"leader_index" : "leader_index"
|
|
}
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
// TESTSETUP
|
|
// TEST[setup:remote_cluster_and_leader_index]
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
POST /follower_index/_ccr/pause_follow
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
// TEARDOWN
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
GET /follower_index/_ccr/info?filter_path=follower_indices.parameters
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
|
|
//////////////////////////
|
|
|
|
The following output from the follow info api describes all the default
|
|
values for the above described index follow request parameters:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
{
|
|
"follower_indices" : [
|
|
{
|
|
"parameters" : {
|
|
"max_read_request_operation_count" : 5120,
|
|
"max_read_request_size" : "32mb",
|
|
"max_outstanding_read_requests" : 12,
|
|
"max_write_request_operation_count" : 5120,
|
|
"max_write_request_size" : "9223372036854775807b",
|
|
"max_outstanding_write_requests" : 9,
|
|
"max_write_buffer_count" : 2147483647,
|
|
"max_write_buffer_size" : "512mb",
|
|
"max_retry_delay" : "500ms",
|
|
"read_poll_timeout" : "1m"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
|
|
--------------------------------------------------
|
|
// TESTRESPONSE |