@@ -99,7 +99,7 @@ example, `cluster.es.eastus2.staging.azure.foundit.no:9400` or
9999[%collapsible%open]
100100.API example
101101====
102- You can also use the <<cluster-update-settings,cluster update settings API>> to
102+ You can also use the <<cluster-update-settings,cluster update settings API>> to
103103add a remote cluster:
104104
105105[source,console]
@@ -200,8 +200,8 @@ image::images/ccr-follower-index.png["The Cross-Cluster Replication page in {kib
200200[%collapsible%open]
201201.API example
202202====
203- You can also use the <<ccr-put-follow,create follower API>> to create follower
204- indices. When you create a follower index, you must reference the remote cluster
203+ You can also use the <<ccr-put-follow,create follower API>> to create follower
204+ indices. When you create a follower index, you must reference the remote cluster
205205and the leader index that you created in the remote cluster.
206206
207207When initiating the follower request, the response returns before the
@@ -255,7 +255,9 @@ POST /server-metrics-follower/_ccr/unfollow
255255You use <<ccr-auto-follow,auto-follow patterns>> to automatically create new
256256followers for rolling time series indices. Whenever the name of a new index on
257257the remote cluster matches the auto-follow pattern, a corresponding follower
258- index is added to the local cluster.
258+ index is added to the local cluster. Note that only indices created on the
259+ remote cluster after the auto-follow pattern is created will be auto-followed:
260+ existing indices on the remote cluster are ignored even if they match the pattern.
259261
260262An auto-follow pattern specifies the remote cluster you want to replicate from,
261263and one or more index patterns that specify the rolling time series indices you
0 commit comments