[
https://issues.apache.org/jira/browse/HBASE-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198414#comment-15198414
]
Geoffrey Jacoby commented on HBASE-12940:
-----------------------------------------
Yes, I noticed those, and they concerned me at first. On a deeper look though,
these appear to be coming from HBase trying to actually set up replication with
remote clusters that aren't actually there. ReplicationPeersZKImpl assumes that
the remote ZooKeeper quorum it's given as the cluster key is a real thing that
it can immediately go talk to. But none of the quorums mentioned in the tests
exist, so the watcher threads on the minicluster are unhappy.
But that doesn't stop us from verifying that the replication_admin wrapper and
ReplicationAdmin class are successfully putting data into _our_ minicluster ZK
instance, and able to get it back out again.
There are also some exceptions related to an unneeded table the existing test
setup creates, and I filed a separate JIRA, HBASE-15472, to take care of that
one.
> Expose listPeerConfigs and getPeerConfig to the HBase shell
> -----------------------------------------------------------
>
> Key: HBASE-12940
> URL: https://issues.apache.org/jira/browse/HBASE-12940
> Project: HBase
> Issue Type: Bug
> Components: shell
> Reporter: Kevin Risden
> Assignee: Geoffrey Jacoby
> Attachments: HBASE-12940-v1.patch, HBASE-12940.patch
>
>
> In HBASE-12867 found that listPeerConfigs and getPeerConfig from
> ReplicationAdmin are not exposed to the HBase shell. This makes looking at
> details for custom replication endpoints and testing of add_peer from
> HBASE-12867 impossible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
