Hi marjana. when you alter to the new replication peer, you only want the new replication data redirect to the new slave cluster ? how about the old data in the master cluster ? is that necessary to migrate to the new slave cluster also ? In our XiaoMi clusters, when doing the migration to a new slave cluster. we would like to do the following:
1. add a disabled peer for the new slave cluster (enqueue the newly written data during the snapshot exporting); 2. create a snapshot in the source cluster; 3. export snapshot to the new slave cluster; 4. enable the disabled peer for new slave cluster; (replicate all the stuck log to new slave). 5. remove the original replication peer. Hope it will be helpful for you. On Wed, Jul 10, 2019 at 8:18 PM marjana <mivko...@us.ibm.com> wrote: > You were thinking something like: > > 1. add_peer NEW_ID 'newZK' > 2. disable_peer ORIGINAL_ID 'originalZK'. > 3. stop slave hbase. move ZK. > 4. start slave hbase. Data starts coming in for NEW_ID peer. > 5. drop_peer ORIGINAL_ID > > Not sure about drop_peer, if I should do it at the end (in case something > goes wrong with the ZK move) or after I disable it at step 2. > Thanks > > > > > > -- > Sent from: > http://apache-hbase.679495.n3.nabble.com/HBase-User-f4020416.html >
