post-resume-follow.asciidoc 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102
  1. [role="xpack"]
  2. [[ccr-post-resume-follow]]
  3. === Resume follower API
  4. ++++
  5. <titleabbrev>Resume follower</titleabbrev>
  6. ++++
  7. Resumes a follower index.
  8. [[ccr-post-resume-follow-request]]
  9. ==== {api-request-title}
  10. //////////////////////////
  11. [source,console]
  12. --------------------------------------------------
  13. PUT /follower_index/_ccr/follow?wait_for_active_shards=1
  14. {
  15. "remote_cluster" : "remote_cluster",
  16. "leader_index" : "leader_index"
  17. }
  18. POST /follower_index/_ccr/pause_follow
  19. --------------------------------------------------
  20. // TESTSETUP
  21. // TEST[setup:remote_cluster_and_leader_index]
  22. [source,console]
  23. --------------------------------------------------
  24. POST /follower_index/_ccr/pause_follow
  25. --------------------------------------------------
  26. // TEARDOWN
  27. //////////////////////////
  28. [source,console]
  29. --------------------------------------------------
  30. POST /<follower_index>/_ccr/resume_follow
  31. {
  32. }
  33. --------------------------------------------------
  34. // TEST[s/<follower_index>/follower_index/]
  35. // TEST[s/<remote_cluster>/remote_cluster/]
  36. // TEST[s/<leader_index>/leader_index/]
  37. [[ccr-post-resume-follow-prereqs]]
  38. ==== {api-prereq-title}
  39. * If the {es} {security-features} are enabled, you must have `write` and `monitor`
  40. index privileges for the follower index. You must have `read` and `monitor`
  41. index privileges for the leader index. You must also have `manage_ccr` cluster
  42. privileges on the cluster that contains the follower index. For more information,
  43. see <<security-privileges>>.
  44. [[ccr-post-resume-follow-desc]]
  45. ==== {api-description-title}
  46. This API resumes a follower index that has been paused either explicitly with
  47. the <<ccr-post-pause-follow, pause follower API>> or implicitly due to
  48. execution that can not be retried due to failure during following. When this API
  49. returns, the follower index will resume fetching operations from the leader index.
  50. [[ccr-post-resume-follow-path-parms]]
  51. ==== {api-path-parms-title}
  52. `<follower_index>`::
  53. (Required, string) The name of the follower index.
  54. [[ccr-post-resume-follow-request-body]]
  55. ==== {api-request-body-title}
  56. include::../follow-request-body.asciidoc[tag=ccr-resume-follow-request-body]
  57. [[ccr-post-resume-follow-examples]]
  58. ==== {api-examples-title}
  59. This example resumes a follower index named `follower_index`:
  60. [source,console]
  61. --------------------------------------------------
  62. POST /follower_index/_ccr/resume_follow
  63. {
  64. "max_read_request_operation_count" : 1024,
  65. "max_outstanding_read_requests" : 16,
  66. "max_read_request_size" : "1024k",
  67. "max_write_request_operation_count" : 32768,
  68. "max_write_request_size" : "16k",
  69. "max_outstanding_write_requests" : 8,
  70. "max_write_buffer_count" : 512,
  71. "max_write_buffer_size" : "512k",
  72. "max_retry_delay" : "10s",
  73. "read_poll_timeout" : "30s"
  74. }
  75. --------------------------------------------------
  76. The API returns the following result:
  77. [source,console-result]
  78. --------------------------------------------------
  79. {
  80. "acknowledged" : true
  81. }
  82. --------------------------------------------------