[HBASE-12706] Support multiple port numbers in ZK quorum string

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0, 2.0.0
• Fix Version/s: 1.1.0, 2.0.0
• Hadoop Flags: Reviewed

Release Note

hbase.zookeeper.quorum configuration now allows servers together with client ports consistent with the way Zookeeper java client accepts the quorum string. In this case, using hbase.zookeeper.clientPort is not needed. eg. hbase.zookeeper.quorum=myserver1:2181,myserver2:20000,myserver3:31111

• Assignee: Stephen Yuan Jiang
• Reporter: Stephen Yuan Jiang
• Due: 17/Mar/15
• Created: 17/Dec/14 22:42
• Updated: 25/Sep/23 11:57
• Resolved: 07/Mar/15 00:51

Description

HBase does not allow the zk quorum string to contain port numbers in this format:

hostname1:port1,hostname2:port2,hostname3:port3

Instead it expects the string to be in this format:

hostname1,hostname2,hostname3:port3

And port 3 is used for all the client ports. We should flex the parsing so that both forms are accepted.

A sample exception:

java.io.IOException: Cluster key passed host1:2181,host2:2181,host3:2181,host4:2181,host5:2181:2181:/hbase is invalid, the format should be:hbase.zookeeper.quorum:hbase.zookeeper.client.port:zookeeper.znode.parent
	at org.apache.hadoop.hbase.zookeeper.ZKUtil.transformClusterKey(ZKUtil.java:403)
	at org.apache.hadoop.hbase.zookeeper.ZKUtil.applyClusterKeyToConf(ZKUtil.java:386)
	at org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getPeerConf(ReplicationPeersZKImpl.java:304)
	at org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.createPeer(ReplicationPeersZKImpl.java:435)

Issue Links

• relates to: PHOENIX-5852 The zkConnectionString in LoadBalance is incorrect
• relates to: PHOENIX-6523 Support for HBase Registry Implementations through Phoenix connection URL