How to test HBase connectivity - ApsaraDB for HBase - Alibaba Cloud Documentation Center

This topic describes how to test connectivity to an ApsaraDB for HBase cluster and lists possible causes of connection failures.

Background information

For security reasons, ApsaraDB for HBase does not support the Internet Control Message Protocol (ICMP). Do not use the ping command to test connectivity. Instead, use Telnet. The service supports both internal access and public access. To connect to your cluster from the internet, you must enable public access.

Procedure

Obtain the ZooKeeper endpoint.
1. Log on to the ApsaraDB for HBase console. On the Clusters page, select your cluster.
2. In the left-side navigation pane, click Database Connection.
3. Find the required connection endpoint.
  Note
  If you connect to the cluster using Thrift or other database services, use the corresponding endpoint and port.
  - For an ApsaraDB for HBase Standard Edition cluster, get the ZooKeeper Address from the Connection Information section.
  - For an ApsaraDB for HBase Performance-enhanced Edition cluster, get the Java API address from the Connection Information section.
ole.dita#hbase-console/card.title.conn.info"> section.
For an ApsaraDB for HBase Performance-enhanced Edition cluster, get the Java API address from the Connection Information section.

Java API address

Connection Information

Test the network connectivity.

Example of a successful connection:

[xx@yy-MacBook-Pro ~]$ telnet  hb-xxxxx-001.hbase.rds.aliyuncs.com 2181
Trying 10.10.10.10...
Connected to hb-xxxxx-001.hbase.rds.aliyuncs.com.
Escape character is '^]'.

Example of a connection failure:

[xx@yy-MacBook-Pro ~]$ telnet  hb-xxxxx-001.hbase.rds.aliyuncs.com 2181
Trying 10.10.10.10...
telnet: connect to address 10.10.10.10: Operation timed out
telnet: Unable to connect to remote host

telnet: Unable to connect to remote host

Possible causes of connection failures

Your client's IP address is not in the cluster's whitelist. For more information, see Configure a whitelist.
_lx2_12x" href="t2012784.dita#concept_2659423">Configure a whitelist.
Outbound traffic from your client is blocked by a firewall or security group rule. For example, if you use an Elastic Compute Service (ECS) instance to connect, ensure that its outbound security group rules allow traffic to the destination IP address and port.
by a firewall or security group rule. For example, if you use an Elastic Compute Service (ECS) instance to connect, ensure that its outbound security group rules allow traffic to the destination IP address and port.
Your client is in a Classic Network, but the cluster is in a virtual private cloud (VPC). By default, a Classic Network cannot communicate with a VPC.
c Network, but the cluster is in a virtual private cloud (VPC). By default, a Classic Network cannot communicate with a VPC.
Your client and cluster are in the same VPC but use different VSwitches. You must add a routing rule to enable communication between the VSwitches.
in the same VPC but use different VSwitches. You must add a routing rule to enable communication between the VSwitches.
Your client and cluster are in different VPCs. By default, VPCs are isolated from each other. To connect the VPCs, use Express Connect.
ferent VPCs. By default, VPCs are isolated from each other. To connect the VPCs, use Express Connect.
Use a leased line to connect to Alibaba Cloud.
ased line to connect to Alibaba Cloud.
If you use an ECS instance to connect to the cluster's public endpoint, the ECS instance itself must have a public IP address and be able to access the internet.
ter's public endpoint, the ECS instance itself must have a public IP address and be able to access the internet.

If the issue persists after you check the items above, contact the ApsaraDB for HBase support team on DingTalk (DingTalk ID: s0s3eg3).