Fixing docs tests after API changes

Author: jasontedor

docs/build.gradle

@@ -1082,15 +1082,15 @@ buildRestTests.setups['calendar_outages_addevent'] = buildRestTests.setups['cale
            ]}
 '''
 
-buildRestTests.setups['leader_cluster'] = buildRestTests.setups['host'] + '''
+buildRestTests.setups['remote_cluster'] = buildRestTests.setups['host'] + '''
   - do:
       cluster.put_settings:
         body:
           persistent:
-            cluster.remote.leader_cluster.seeds: $transport_host
+            cluster.remote.remote_cluster.seeds: $transport_host
 '''
 
-buildRestTests.setups['leader_cluster_and_leader_index'] = buildRestTests.setups['leader_cluster'] + '''
+buildRestTests.setups['remote_cluster_and_leader_index'] = buildRestTests.setups['remote_cluster'] + '''
   - do:
       indices.create:
         index: leader_index

docs/reference/ccr/apis/auto-follow/delete-auto-follow-pattern.asciidoc

@@ -20,7 +20,7 @@ This API deletes a configured auto-follow pattern collection.
 --------------------------------------------------
 PUT /_ccr/auto_follow/my_auto_follow_pattern
 {
-  "leader_cluster" : "leader_cluster",
+  "remote_cluster" : "remote_cluster",
   "leader_index_patterns" :
   [
     "leader_index"
@@ -29,7 +29,7 @@ PUT /_ccr/auto_follow/my_auto_follow_pattern
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[setup:leader_cluster]
+// TEST[setup:remote_cluster]
 // TESTSETUP
 
 //////////////////////////
@@ -55,7 +55,7 @@ This example deletes an auto-follow pattern collection named
 DELETE /_ccr/auto_follow/my_auto_follow_pattern
 --------------------------------------------------
 // CONSOLE
-// TEST[setup:leader_cluster]
+// TEST[setup:remote_cluster]
 
 The API returns the following result:
 

docs/reference/ccr/apis/auto-follow/get-auto-follow-pattern.asciidoc

@@ -21,7 +21,7 @@ specified auto-follow pattern collection.
 --------------------------------------------------
 PUT /_ccr/auto_follow/my_auto_follow_pattern
 {
-  "leader_cluster" : "leader_cluster",
+  "remote_cluster" : "remote_cluster",
   "leader_index_patterns" :
   [
     "leader_index*"
@@ -30,7 +30,7 @@ PUT /_ccr/auto_follow/my_auto_follow_pattern
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[setup:leader_cluster]
+// TEST[setup:remote_cluster]
 // TESTSETUP
 
 [source,js]
@@ -72,7 +72,7 @@ named `my_auto_follow_pattern`:
 GET /_ccr/auto_follow/my_auto_follow_pattern
 --------------------------------------------------
 // CONSOLE
-// TEST[setup:leader_cluster]
+// TEST[setup:remote_cluster]
 
 The API returns the following result:
 
@@ -81,7 +81,7 @@ The API returns the following result:
 {
   "my_auto_follow_pattern" :
   {
-    "leader_cluster" : "leader_cluster",
+    "remote_cluster" : "remote_cluster",
     "leader_index_patterns" :
     [
       "leader_index*"

docs/reference/ccr/apis/auto-follow/put-auto-follow-pattern.asciidoc

@@ -21,7 +21,7 @@ configured as follower indices.
 --------------------------------------------------
 PUT /_ccr/auto_follow/<auto_follow_pattern_name>
 {
-  "leader_cluster" : "<leader_cluster>",
+  "remote_cluster" : "<remote_cluster>",
   "leader_index_patterns" :
   [
     "<leader_index_pattern>"
@@ -30,9 +30,9 @@ PUT /_ccr/auto_follow/<auto_follow_pattern_name>
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[setup:leader_cluster]
+// TEST[setup:remote_cluster]
 // TEST[s/<auto_follow_pattern_name>/auto_follow_pattern_name/]
-// TEST[s/<leader_cluster>/leader_cluster/]
+// TEST[s/<remote_cluster>/remote_cluster/]
 // TEST[s/<leader_index_patterns>/leader_index*/]
 // TEST[s/<follow_index_pattern>/{{leader_index}}-follower/]
 
@@ -52,13 +52,13 @@ DELETE /_ccr/auto_follow/auto_follow_pattern_name
   (string) name of the collection of auto-follow patterns
 
 ==== Request Body
-`leader_cluster`::
+`remote_cluster`::
   (required string) the <<modules-remote-clusters,remote cluster>> containing the
   leader indices to match against
 
 `leader_index_patterns`::
   (array) an array of simple index patterns to match against indices in the
-  remote cluster specified by the `leader_cluster` field
+  remote cluster specified by the `remote_cluster` field
 
 `follow_index_pattern`::
   (string) the name of follower index; the template `{{leader_index}}` can be
@@ -75,7 +75,7 @@ This example creates an auto-follow pattern named `my_auto_follow_pattern`:
 --------------------------------------------------
 PUT /_ccr/auto_follow/my_auto_follow_pattern
 {
-  "leader_cluster" : "leader_cluster",
+  "remote_cluster" : "remote_cluster",
   "leader_index_patterns" :
   [
     "leader_index*"
@@ -84,7 +84,7 @@ PUT /_ccr/auto_follow/my_auto_follow_pattern
 }
 --------------------------------------------------
 // CONSOLE
-// TEST[setup:leader_cluster]
+// TEST[setup:remote_cluster]
 
 The API returns the following result:
 

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

@@ -1,30 +1,44 @@
-`max_batch_operation_count`::
-  (integer) the maximum number of operations to pull per fetch from the remote
+`max_read_request_operation_count`::
+  (integer) the maximum number of operations to pull per read from the remote
   cluster
 
-`max_concurrent_read_batches`::
-  (long) the maximum number of concurrent fetches from the remote cluster
+`max_outstanding_read_requests`::
+  (long) the maximum number of outstanding reads requests from the remote
+  cluster
 
-`max_batch_size`::
-  (<<byte-units,byte value>>) the maximum size in bytes of batches pulled per
-  fetch 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_concurrent_write_batches`::
-  (integer) the maximum number of concurrent writes on the following index
+`max_write_request_operation_count`::
+  (integer) the maximum number of operations per bulk write request executed on
+  the follower
 
-`max_write_buffer_size`::
+`max_write_request_size`::
+  (integer) 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, fetches from the remote cluster will be
-  deferred until the number of queued operations goes below the limit
+  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`::
+  (integer) 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
 
-`poll_timeout`::
+`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 fetch from the leader again
+  immediately attempt to read from the leader again