ApsaraDB for HBase clusters use two node roles: master nodes handle cluster coordination and metadata management, while core nodes store and process data. Because their roles differ, each has distinct specification options. The tables below list available CPU and memory combinations by engine.
ApsaraDB for HBase
The table below lists master node and core node specifications for ApsaraDB for HBase Standard Edition and Performance-enhanced Edition.
| Engine | Master node | Core node |
|---|
| ApsaraDB for HBase Standard Edition | - 4 cores, 16 GB memory (dedicated resources) —
hbase.sn2.large - 4 cores, 8 GB memory (dedicated resources) —
hbase.sn1.large - 8 cores, 16 GB memory (dedicated resources) —
hbase.sn1.2xlarge - 8 cores, 32 GB memory (dedicated resources) —
hbase.sn2.2xlarge - 16 cores, 32 GB memory (dedicated resources) —
hbase.sn1.4xlarge - 16 cores, 64 GB memory (dedicated resources) —
hbase.sn2.4xlarge - 32 cores, 128 GB memory (dedicated resources) —
hbase.sn2.8xlarge
| Memory:CPU ratio 2:1 — compatible disk types: cloud_ssd, cloud_essd_pl1, cloud_efficiency- 8 cores, 16 GB memory (dedicated resources) —
hbase.sn1.2xlarge - 16 cores, 32 GB memory (dedicated resources) —
hbase.sn1.4xlarge - 32 cores, 64 GB memory (dedicated resources) —
hbase.sn1.8xlarge
Memory:CPU ratio 4:1 — compatible disk types: cloud_ssd, cloud_essd_pl1, cloud_efficiency- 4 cores, 16 GB memory (dedicated resources) —
hbase.sn2.large
Important Only ApsaraDB for HBase Performance-enhanced Edition supports this specification. - 8 cores, 32 GB memory (dedicated resources) —
hbase.sn2.2xlarge - 16 cores, 64 GB memory (dedicated resources) —
hbase.sn2.4xlarge - 32 cores, 128 GB memory (dedicated resources) —
hbase.sn2.8xlarge
Local HDDs — disk type: local_hdd_pro- 16 cores, 64 GB memory (local HDDs and dedicated resources) —
hbase.d1.4xlarge - 24 cores, 96 GB memory (local HDDs and dedicated resources) —
hbase.d1.6xlarge - 32 cores, 128 GB memory (local HDDs and dedicated resources) —
hbase.d1.8xlarge - 40 cores, 176 GB memory (local HDDs and dedicated resources) —
hbase.d1.10xlarge
Local SSDs — disk type: local_ssd_pro- 4 cores, 32 GB memory (local SSDs) —
hbase.i2.xlarge - 8 cores, 64 GB memory (local SSDs) —
hbase.i2.2xlarge - 16 cores, 128 GB memory (local SSDs) —
hbase.i2.4xlarge - 32 cores, 256 GB memory (local SSDs) —
hbase.i2.8xlarge
|
| ApsaraDB for HBase Performance-enhanced Edition | - 4 cores, 8 GB memory (dedicated resources) —
hbase.sn1.large - 4 cores, 16 GB memory (dedicated resources) —
hbase.sn2.large - 8 cores, 16 GB memory (dedicated resources) —
hbase.sn1.2xlarge - 8 cores, 32 GB memory (dedicated resources) —
hbase.sn2.2xlarge - 16 cores, 32 GB memory (dedicated resources) —
hbase.sn1.4xlarge - 16 cores, 64 GB memory (dedicated resources) —
hbase.sn2.4xlarge - 32 cores, 64 GB memory (dedicated resources) —
hbase.sn1.8xlarge - 32 cores, 128 GB memory (dedicated resources) —
hbase.sn2.8xlarge
| Same as ApsaraDB for HBase Standard Edition. |
Big DataHub Service (BDS)
BDS does not use a dedicated master node. Leave the master node parameter blank when creating a BDS cluster.
| Engine | Master node | Core node |
|---|
| Big DataHub Service (BDS) | You can enter an empty string. | - 4 cores, 8 GB memory (dedicated resources) —
hbase.sn1.large - 8 cores, 16 GB memory (dedicated resources) —
hbase.sn1.2xlarge - 16 cores, 32 GB memory (dedicated resources) —
hbase.sn1.4xlarge - 32 cores, 128 GB memory (dedicated resources) —
hbase.sn1.8xlarge
|
ApsaraDB for HBase in single-node mode
Note ApsaraDB for HBase in single-node mode is no longer available for purchase. If you purchased an instance earlier, you can continue to use it.
Single-node mode uses only a core node. To create an instance in single-node mode, call the CreateCluster operation with NodeCount set to 1 and core_instance_quantity set to 1.
| Engine | Master node | Core node |
|---|
| ApsaraDB for HBase in single-node mode | You can enter an empty string. | - 2 cores, 4 GB memory —
hbase.sn1ne.large - 4 cores, 8 GB memory —
hbase.sn1ne.xlarge
|