From 1bffc9601a371aa7a3be1ae56057191b748a77a1 Mon Sep 17 00:00:00 2001 From: Abby <78209557+abby-cyber@users.noreply.github.com> Date: Wed, 14 Sep 2022 12:03:33 +0800 Subject: [PATCH 1/2] add-note-for-cluster-sync --- .../replication-between-clusters.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs-2.0/synchronization-and-migration/replication-between-clusters.md b/docs-2.0/synchronization-and-migration/replication-between-clusters.md index 8b6fe2525b6..84fe9396f9a 100644 --- a/docs-2.0/synchronization-and-migration/replication-between-clusters.md +++ b/docs-2.0/synchronization-and-migration/replication-between-clusters.md @@ -318,6 +318,10 @@ To migrate data or implement disaster recovery, manually switch between the prim Before the switching, set up a listener for the new primary cluster, and a drainer for the new secondary cluster. In the following example, the listener has IP address 192.168.10.105 and drainer 192.168.10.106. +!!! caution + + DO NOT write data to the master cluster and make sure that the data in the master cluster has been synchronized to the slave cluster before switching between master and slave clusters. + 1. Log into the primary cluster and remove the old drainer and listener. ```ngql @@ -345,7 +349,6 @@ To migrate data or implement disaster recovery, manually switch between the prim ```ngql nebula> SIGN IN DRAINER SERVICE(192.168.10.106:9889); nebula> ADD LISTENER SYNC META 192.168.10.105:9569 STORAGE 192.168.10.105:9789 TO SPACE basketballplayer; - nebula> REMOVE DRAINER; ``` 5. Log into the old primary cluster and change it to the new secondary cluster. From 6d0861c2d75fbcda370ae721fa531922bc33acc3 Mon Sep 17 00:00:00 2001 From: Abby <78209557+abby-cyber@users.noreply.github.com> Date: Thu, 15 Sep 2022 14:01:06 +0800 Subject: [PATCH 2/2] Update replication-between-clusters.md --- .../replication-between-clusters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-2.0/synchronization-and-migration/replication-between-clusters.md b/docs-2.0/synchronization-and-migration/replication-between-clusters.md index 84fe9396f9a..1c27ec8846d 100644 --- a/docs-2.0/synchronization-and-migration/replication-between-clusters.md +++ b/docs-2.0/synchronization-and-migration/replication-between-clusters.md @@ -320,7 +320,7 @@ To migrate data or implement disaster recovery, manually switch between the prim !!! caution - DO NOT write data to the master cluster and make sure that the data in the master cluster has been synchronized to the slave cluster before switching between master and slave clusters. + DO NOT write data to the primary cluster and make sure that the data in the primary cluster has been synchronized to the secondary cluster before switching between primary and secondary clusters. 1. Log into the primary cluster and remove the old drainer and listener.