[HBASE-21771] Cluster key in Master UI is incorrect

• Type: Bug
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-alpha-1, 2.1.0, 2.0.0
• Component/s: Replication, UI, Usability
• Assignee: Sean Busbey
• Reporter: Sean Busbey
• Created: 24/Jan/19 16:36
• Updated: 13/Jun/22 15:42

Description

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:

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"]

However, on my example cluster with ZK quorum with 3 servers, the master ui gives this:

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.

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.