[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751857#comment-16751857
]
Hadoop QA commented on HBASE-21771:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} HBASE-21771 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21771 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/15729/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Cluster key in Master UI is incorrect
> -------------------------------------
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
> Affects Versions: 3.0.0, 2.1.0, 2.0.0
> Reporter: Sean Busbey
> Assignee: Sakthi
> Priority: Major
> Fix For: 3.0.0, 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbase Key to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
