# How to handle pre-existing indices using Auto-Follow **URL:** \ **Category:** Cross-Cluster Replication\ **Created:** [September 16, 2026, 11:07am UTC](https://forum.opensearch.org/t/how-to-handle-pre-existing-indices-using-auto-follow/28289 "2026-09-16T11:07:38Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![farman](https://avatars.discourse-cdn.com/v4/letter/f/f14d63/32.png) [@farman](https://forum.opensearch.org/u/farman)\ **Post date:** [September 16, 2026, 11:07am UTC](https://forum.opensearch.org/t/how-to-handle-pre-existing-indices-using-auto-follow/28289/1 "2026-09-16T11:07:38Z")
**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser): **Describe the issue** : If I am using Auto-Follow for replication, then, follower indices are created automatically based on “pattern” and “follower\_index\_pattern” specified in CCR rule. If for some reason CCR is stopped and then recreated between the same leader and follower clusters and using the same “pattern” and “follower\_index\_pattern”, then, what will happen to already existing follower indices. Will they be overwritten or skipped or will an error be raised by CCR plugin **Configuration** : **Relevant Logs or Screenshots** : ---
**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\ **Post date:** [September 23, 2026, 12:59pm UTC](https://forum.opensearch.org/t/how-to-handle-pre-existing-indices-using-auto-follow/28289/2 "2026-09-23T12:59:38Z")
@farman What do you mean by `CCR is stopped`? Are you referring to deleting the replication rule ([Auto-follow for cross-cluster replication | OpenSearch Documentation](https://docs.opensearch.org/latest/tuning-your-cluster/replication-plugin/auto-follow/#delete-a-replication-rule)) or stopping/disconnecting the leader cluster? I had no issues when I deleted auto-follow replication and recreated it. The replication was working, and new documents were added from the leader. The existing documents in the follower index remained. I had a different result when I stopped the leader and waited 2 minutes before starting it again. The replication didn’t resume automatically either for auto-follow or individual replication. I had to use `_resume` with the `force_resume` option. However, the indices were recreated, and all documents were fully resynced. > **[Limitations - Force-resume replication](https://docs.opensearch.org/latest/tuning-your-cluster/replication-plugin/force-resume/#limitations)** > > Introduced 3.8 | When cross-cluster replication is paused for longer than the retention lease duration (controlled by the index.soft\_deletes.retention\_lease.period setting on... ---
**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\ **Post date:** [September 23, 2026, 1:32pm UTC](https://forum.opensearch.org/t/how-to-handle-pre-existing-indices-using-auto-follow/28289/3 "2026-09-23T13:32:58Z")
@farman I made a second attempt by stopping the leader cluster, and this time replication resumed automatically. However, if the leader cluster is down or replication is stopped/paused for more than 12 hours, you’ll need to force-resume, which will recreate all indices. > **[Request body fields - Cross-Cluster Replication API](https://docs.opensearch.org/latest/tuning-your-cluster/replication-plugin/api/#request-body-fields-1)** > > Use these replication operations to programmatically manage cross-cluster replication. ---
**Author:** ![farman](https://avatars.discourse-cdn.com/v4/letter/f/f14d63/32.png) [@farman](https://forum.opensearch.org/u/farman)\ **Post date:** [September 24, 2026, 10:11am UTC](https://forum.opensearch.org/t/how-to-handle-pre-existing-indices-using-auto-follow/28289/4 "2026-09-24T10:11:14Z")
Thanks Pablo. I assume your second reply is the conclusive one.