follow-request-body.asciidoc 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. [testenv="platinum"]
  2. `max_read_request_operation_count`::
  3. (integer) The maximum number of operations to pull per read from the remote
  4. cluster.
  5. `max_outstanding_read_requests`::
  6. (long) The maximum number of outstanding reads requests from the remote
  7. cluster.
  8. `max_read_request_size`::
  9. (<<byte-units,byte value>>) The maximum size in bytes of per read of a batch
  10. of operations pulled from the remote cluster.
  11. `max_write_request_operation_count`::
  12. (integer) The maximum number of operations per bulk write request executed on
  13. the follower.
  14. `max_write_request_size`::
  15. (<<byte-units,byte value>>) The maximum total bytes of operations per bulk write request
  16. executed on the follower.
  17. `max_outstanding_write_requests`::
  18. (integer) The maximum number of outstanding write requests on the follower.
  19. `max_write_buffer_count`::
  20. (integer) The maximum number of operations that can be queued for writing.
  21. When this limit is reached, reads from the remote cluster will be deferred
  22. until the number of queued operations goes below the limit.
  23. `max_write_buffer_size`::
  24. (<<byte-units,byte value>>) The maximum total bytes of operations that can be
  25. queued for
  26. writing. When this limit is reached, reads from the remote cluster will be
  27. deferred until the total bytes of queued operations goes below the limit.
  28. `max_retry_delay`::
  29. (<<time-units,time value>>) The maximum time to wait before retrying an
  30. operation that failed exceptionally. An exponential backoff strategy is
  31. employed when retrying.
  32. `read_poll_timeout`::
  33. (<<time-units,time value>>) The maximum time to wait for new operations on the
  34. remote cluster when the follower index is synchronized with the leader index.
  35. When the timeout has elapsed, the poll for operations will return to the
  36. follower so that it can update some statistics. Then the follower will
  37. immediately attempt to read from the leader again.
  38. ===== Default values
  39. //////////////////////////
  40. [source,js]
  41. --------------------------------------------------
  42. PUT /follower_index/_ccr/follow?wait_for_active_shards=1
  43. {
  44. "remote_cluster" : "remote_cluster",
  45. "leader_index" : "leader_index"
  46. }
  47. --------------------------------------------------
  48. // CONSOLE
  49. // TESTSETUP
  50. // TEST[setup:remote_cluster_and_leader_index]
  51. [source,js]
  52. --------------------------------------------------
  53. POST /follower_index/_ccr/pause_follow
  54. --------------------------------------------------
  55. // CONSOLE
  56. // TEARDOWN
  57. [source,js]
  58. --------------------------------------------------
  59. GET /follower_index/_ccr/info?filter_path=follower_indices.parameters
  60. --------------------------------------------------
  61. // CONSOLE
  62. //////////////////////////
  63. The following output from the follow info api describes all the default
  64. values for the above described index follow request parameters:
  65. [source,js]
  66. --------------------------------------------------
  67. {
  68. "follower_indices" : [
  69. {
  70. "parameters" : {
  71. "max_read_request_operation_count" : 5120,
  72. "max_read_request_size" : "32mb",
  73. "max_outstanding_read_requests" : 12,
  74. "max_write_request_operation_count" : 5120,
  75. "max_write_request_size" : "9223372036854775807b",
  76. "max_outstanding_write_requests" : 9,
  77. "max_write_buffer_count" : 2147483647,
  78. "max_write_buffer_size" : "512mb",
  79. "max_retry_delay" : "500ms",
  80. "read_poll_timeout" : "1m"
  81. }
  82. }
  83. ]
  84. }
  85. --------------------------------------------------
  86. // TESTRESPONSE