2019-01-18 10:37:21 -05:00
|
|
|
[role="xpack"]
|
|
|
|
[testenv="platinum"]
|
|
|
|
[[ccr-get-follow-info]]
|
|
|
|
=== Get follower info API
|
|
|
|
++++
|
|
|
|
<titleabbrev>Get follower info</titleabbrev>
|
|
|
|
++++
|
|
|
|
|
|
|
|
Retrieves information about all follower indices.
|
|
|
|
|
2019-07-04 11:22:17 -04:00
|
|
|
[[ccr-get-follow-info-request]]
|
|
|
|
==== {api-request-title}
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
//////////////////////////
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
--------------------------------------------------
|
2019-01-29 13:47:29 -05:00
|
|
|
PUT /follower_index/_ccr/follow?wait_for_active_shards=1
|
2019-01-18 10:37:21 -05:00
|
|
|
{
|
|
|
|
"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 /<index>/_ccr/info
|
|
|
|
--------------------------------------------------
|
|
|
|
// CONSOLE
|
|
|
|
// TEST[s/<index>/follower_index/]
|
|
|
|
|
2019-07-04 11:22:17 -04:00
|
|
|
[[ccr-get-follow-info-prereqs]]
|
|
|
|
==== {api-prereq-title}
|
2019-01-18 10:37:21 -05:00
|
|
|
|
2019-07-04 11:22:17 -04:00
|
|
|
* If the {es} {security-features} are enabled, you must have `monitor` cluster
|
|
|
|
privileges. For more information, see
|
|
|
|
{stack-ov}/security-privileges.html[Security privileges].
|
|
|
|
|
|
|
|
[[ccr-get-follow-info-desc]]
|
|
|
|
==== {api-description-title}
|
|
|
|
|
|
|
|
This API lists the parameters and the status for each follower index.
|
|
|
|
For example, the results include follower index names, leader index names,
|
|
|
|
replication options and whether the follower indices are active or paused.
|
|
|
|
|
|
|
|
[[ccr-get-follow-info-path-parms]]
|
|
|
|
==== {api-path-parms-title}
|
|
|
|
|
2019-07-12 11:26:31 -04:00
|
|
|
`<index>`::
|
|
|
|
(Required, string) A comma-delimited list of follower index patterns.
|
2019-07-04 11:22:17 -04:00
|
|
|
|
|
|
|
[[ccr-get-follow-info-response-body]]
|
|
|
|
==== {api-response-body-title}
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
This API returns the following information:
|
|
|
|
|
|
|
|
`follower_indices`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(array) An array of follower index statistics.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
The `indices` array consists of objects containing several fields:
|
|
|
|
|
|
|
|
`indices[].follower_index`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(string) The name of the follower index.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].remote_cluster`::
|
|
|
|
(string) The <<modules-remote-clusters,remote cluster>> that contains the
|
2019-07-04 11:22:17 -04:00
|
|
|
leader index.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].leader_index`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(string) The name of the index in the leader cluster that is followed.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].status`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(string) Whether index following is `active` or `paused`.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(object) An object that encapsulates {ccr} parameters.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
The `parameters` contains the following fields:
|
|
|
|
|
|
|
|
`indices[].parameters.max_read_request_operation_count`::
|
|
|
|
(integer) The maximum number of operations to pull per read from the remote
|
2019-07-04 11:22:17 -04:00
|
|
|
cluster.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.max_outstanding_read_requests`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(long) The maximum number of outstanding read requests from the remote cluster.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.max_read_request_size`::
|
|
|
|
(<<byte-units,byte value>>) The maximum size in bytes of per read of a batch
|
2019-07-04 11:22:17 -04:00
|
|
|
of operations pulled from the remote cluster.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.max_write_request_operation_count`::
|
|
|
|
(integer) The maximum number of operations per bulk write request executed on
|
2019-07-04 11:22:17 -04:00
|
|
|
the follower.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.max_write_request_size`::
|
|
|
|
(<<byte-units,byte value>>) The maximum total bytes of operations per bulk
|
2019-07-04 11:22:17 -04:00
|
|
|
write request executed on the follower.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.max_outstanding_write_requests`::
|
2019-07-04 11:22:17 -04:00
|
|
|
(integer) The maximum number of outstanding write requests on the follower.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.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 are deferred until
|
2019-07-04 11:22:17 -04:00
|
|
|
the number of queued operations goes below the limit.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.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
|
2019-07-04 11:22:17 -04:00
|
|
|
are deferred until the total bytes of queued operations goes below the limit.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.max_retry_delay`::
|
|
|
|
(<<time-units,time value>>) The maximum time to wait before retrying an
|
|
|
|
operation that failed exceptionally. An exponential backoff strategy is
|
2019-07-04 11:22:17 -04:00
|
|
|
employed when retrying.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
`indices[].parameters.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 returns to the follower
|
|
|
|
so that it can update some statistics, then the follower immediately attempts
|
2019-07-04 11:22:17 -04:00
|
|
|
to read from the leader again.
|
2019-01-18 10:37:21 -05:00
|
|
|
|
2019-07-04 11:22:17 -04:00
|
|
|
[[ccr-get-follow-info-examples]]
|
|
|
|
==== {api-examples-title}
|
2019-01-18 10:37:21 -05:00
|
|
|
|
|
|
|
This example retrieves follower info:
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
--------------------------------------------------
|
|
|
|
GET /follower_index/_ccr/info
|
|
|
|
--------------------------------------------------
|
|
|
|
// CONSOLE
|
|
|
|
|
|
|
|
The API returns the following results:
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
--------------------------------------------------
|
|
|
|
{
|
|
|
|
"follower_indices" : [
|
|
|
|
{
|
|
|
|
"follower_index" : "follower_index",
|
|
|
|
"remote_cluster" : "remote_cluster",
|
|
|
|
"leader_index" : "leader_index",
|
|
|
|
"status" : "active",
|
|
|
|
"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
|