This page answers common questions about ApsaraDB for HBase, organized by topic.
General
What scenarios is ApsaraDB for HBase suitable for?
ApsaraDB for HBase is a cost-effective, all-in-one data processing platform built on Apache HBase and its ecosystem. It covers the full data lifecycle—processing, storage, and analysis—in a single service.
What are the advantages of ApsaraDB for HBase clusters over self-managed HBase clusters and E-MapReduce (EMR) HBase clusters?
ApsaraDB for HBase clusters are cost-effective and provide all-in-one data processing capabilities.
Cluster setup and purchase
An error says database resources are insufficient when I try to purchase a cluster. What should I do?
The selected region has run out of available resources. Wait up to one day for capacity to free up, then try again. If you need a cluster immediately, submit a ticket.
I paid for a cluster, but it doesn't appear in the console. What's happening?
Cluster creation takes a few minutes. The cluster only appears in the console after it is fully provisioned. Refresh the console after a few minutes.
A newly created cluster cannot connect to open source components. Why?
For security, newly created clusters are not accessible by default.
The disk capacity of my cluster is too small. Can I expand it?
Yes. Expand disk capacity directly from the ApsaraDB for HBase console.
Connectivity
I configured the ZooKeeper address in my client, but I still can't connect to the cluster. How do I troubleshoot?
Follow the steps in Test connectivity to diagnose and fix the connection issue.
Data migration
How do I migrate data from a CDH or HDP cluster to ApsaraDB for HBase?
ApsaraDB for HBase supports live migration with no service downtime—your business workloads keep running during the migration.
This applies to on-premises Cloudera Distributed Hadoop (CDH) or Hortonworks Data Platform (HDP) clusters, as well as self-managed CDH or HDP clusters running on Elastic Compute Service (ECS) instances.
For data processed by Apache Hive or Apache MapReduce, choose one of the following methods:
Use Apache Spark on ApsaraDB for HBase: Upgrade your cluster to use Apache Spark components. This improves processing efficiency and reduces costs.
Connect to an EMR cluster: Link your ApsaraDB for HBase cluster to an E-MapReduce (EMR) cluster and continue using the Hive and MapReduce services from EMR. ApsaraDB for HBase integrates with EMR.
Resource cleanup
After I release an ApsaraDB for HBase cluster and try to delete its VPC, I get an error saying the VPC has an existing security group. What should I do?
The security group is deleted asynchronously—approximately one hour after the cluster is released. Wait one hour after releasing the cluster before deleting the virtual private cloud (VPC).
If you attempt to delete the VPC before the security group is removed, the deletion will fail with an error indicating a security group still exists in the VPC. Wait the full hour and try again.
Maven dependency
In a Maven project, can hbase-client depend on org.apache.hbase?
Yes. Use the following dependency versions based on your hbase-client version:
hbase-client V1.x:
<dependency>
<groupId>org.apache.hbase</groupId>
<artifactId>hbase-client</artifactId>
<version>1.1.3</version>
</dependency>hbase-client V2.x:
<dependency>
<groupId>org.apache.hbase</groupId>
<artifactId>hbase-client</artifactId>
<version>2.0.5</version>
</dependency>