[
https://issues.apache.org/jira/browse/HBASE-20425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447834#comment-16447834
]
Zheng Hu commented on HBASE-20425:
----------------------------------
Checked the code, the rs only attach the cluster id into WALs in
ReplicationSouce (by ClusterMarkingEntryFilter), so it won't add clusterIds
when write the remote WAL in theory. And I've write a UT for this case, and
it passed.
IMO, we just need to commit the UT to ensure that remote WALs won't have the
cluster id of active cluster.
> Do not write the cluster id of the current active cluster when writing remote
> WAL
> ---------------------------------------------------------------------------------
>
> Key: HBASE-20425
> URL: https://issues.apache.org/jira/browse/HBASE-20425
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Zheng Hu
> Priority: Major
> Attachments: HBASE-20425.HBASE-19064.v1.patch,
> HBASE-20425.HBASE-19064.v1.patch
>
>
> The wal entries which are replayed when converting a cluster from S to DA
> need to be replicated back to the old A cluster. if we write the cluster id
> of A into the wal entries, we will skip replicating them...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
