From f3f35f75f6f872d292661ad5b2b9237f26b5a9ec 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 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) 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 777c5fa7626..c6f672cc8d9 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. ```bash @@ -344,8 +348,7 @@ To migrate data or implement disaster recovery, manually switch between the prim ```bash nebula> SIGN IN DRAINER SERVICE(192.168.10.106:9889); - nebula> ADD LISTENER SYNC META 192.168.10.105:9559 STORAGE 192.168.10.105:9789 TO SPACE basketballplayer; - nebula> REMOVE DRAINER; + nebula> ADD LISTENER SYNC META 192.168.10.105:9569 STORAGE 192.168.10.105:9789 TO SPACE basketballplayer; ``` 5. Log into the old primary cluster and change it to the new secondary cluster. From accf035188e2c35ac5bff64be744d4e703fba4ef Mon Sep 17 00:00:00 2001 From: Abby <78209557+abby-cyber@users.noreply.github.com> Date: Thu, 15 Sep 2022 14:03:33 +0800 Subject: [PATCH 2/2] fix term --- .../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 c6f672cc8d9..554a14da8b4 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.