[
https://issues.apache.org/jira/browse/HBASE-19630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303739#comment-16303739
]
Guanghao Zhang commented on HBASE-19630:
----------------------------------------
Yes. In RS side, it always getPeerConf when create a new ReplicationPeer. If
got a exception, the rs can't add a new replication source.
{code}
Configuration otherConf;
try {
otherConf = HBaseConfiguration.createClusterConf(this.conf,
peerConfig.getClusterKey());
} catch (IOException e) {
LOG.error("Can't get peer configuration for peerId=" + peerId + "
because:", e);
return null;
}
{code}
And the key thing in createClusterConf is validate the ClusterKey.
> Add peer cluster key check when add new replication peer
> --------------------------------------------------------
>
> Key: HBASE-19630
> URL: https://issues.apache.org/jira/browse/HBASE-19630
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2, Replication
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Fix For: HBASE-19397
>
> Attachments: HBASE-19630.HBASE-19397.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
