This topic provides answers to some commonly asked questions about using ApsaraDB for HBase.
What scenarios is ApsaraDB for HBase suitable for?
ApsaraDB for HBase is a cost-effective and all-in-one data processing platform based on Apache HBase and the Apache HBase ecosystem. ApsaraDB for HBase provides closed-loop capabilities to process, store, and analyze data. This allows you to implement all-in-one data processing at a low cost.
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.
How do I migrate data from an on-premises Cloudera Distributed Hadoop (CDH) or Hortonworks Data Platform (HDP) cluster or a self-managed CDH or HDP cluster deployed on an Elastic Compute Service (ECS) instance to an ApsaraDB for HBase cluster?
ApsaraDB for HBase supports data migration without service downtime. When you migrate data from a CDH or HDP cluster to an ApsaraDB for HBase cluster, your business workloads are not affected. For the data that is processed by components such as Apache Hive and Apache MapReduce, you can use the following methods:
Upgrade your ApsaraDB for HBase cluster so that the cluster can use the components of Apache Spark to process data. This method improves efficiency and reduces costs.
Connect an ApsaraDB for HBase cluster to an EMR cluster. This allows you to use the Hive and MapReduce services of EMR to process data. ApsaraDB for HBase can be seamlessly connected to EMR.
When I purchase an ApsaraDB for HBase cluster, an error message appears to indicate that the database resources are insufficient. Why does the purchase fail?
This error occurs because the database resources in the specified region have been sold out. You need to wait until sufficient resources are available and then try again. In most cases, you need to wait at most one day. If you need an ApsaraDB for HBase cluster for urgency, submit a ticket.
Why does not a purchased cluster appear in the console after I pay for it?
A cluster is not displayed in the console while the system is creating it. It takes a few minutes to create a cluster. After the cluster is created, you can view the cluster in the console.
I configured the ZooKeeper address of the cluster in my client. Why am I still unable to use the client to connect to my ApsaraDB for HBase cluster?
For more information about how to troubleshoot connection failures, see Test connectivity.
Why am I unable to connect my newly created ApsaraDB for HBase cluster to an open source component?
For security purposes, a newly created cluster cannot be accessed by default.
The disk capacity of an ApsaraDB for HBase cluster is too small. Can I increase the disk capacity?
Yes, you can increase the disk capacity in the ApsaraDB for HBase console.
What do I do if the system reports an error indicating that a security group exists in the virtual private cloud (VPC) and the VPC cannot be deleted when I delete the VPC after I release an ApsaraDB for HBase cluster?
The release of an ApsaraDB for HBase cluster and the deletion of its security group are performed asynchronously. The security group is deleted approximately one hour after the ApsaraDB for HBase cluster is released. Therefore, we recommend that you delete the VPC to which the security group belongs one hour after the ApsaraDB for HBase cluster is released.
In a Maven project, can hbase-client depend on org.apache.hbase?
Yes, hbase-client V1.x can depend on org.apache.hbase V1.1.3 and hbase-client V2.x can depend on org.apache.hbase V2.0.5.