The following tables describe the specifications of master nodes and core nodes that you can select based on different engines.

Engine Master node Core node
ApsaraDB for HBase Standard Edition
  • 4-core 16 GB (dedicated resources) hbase.sn2.large
  • 4-core 8 GB (dedicated resources) hbase.sn1.large
  • 8-core 16 GB (dedicated resources) hbase.sn1.2xlarge
  • 8-core 32 GB (dedicated resources) hbase.sn2.2xlarge
  • 16-core 32 GB (dedicated resources) hbase.sn1.4xlarge
  • 16-core 64 GB (dedicated resources) hbase.sn2.4xlarge
  • 4-core 8 GB (general-purpose nodes)
  • If the ratio of memory to CPU cores is 2:1, you can use the following disk types: cloud_ssd, cloud_essd_pl1, and cloud_efficiency.
    • 4-core 8 GB (dedicated resources)
    • 8-core 16 GB (dedicated resources)

      hbase.sn1.2xlarge

    • 16-core 32 GB (dedicated resources)

      hbase.sn1.4xlarge

    • 32-core 64 GB (dedicated resources)

      hbase.sn1.8xlarge

  • If the ratio of memory to CPU cores is 4:1, you can use the following disk types: cloud_ssd, cloud_essd_pl1, and cloud_efficiency.
    • 4-core 32 GB (dedicated resources)

      hbase.sn2.large

    • 8-core 32 GB (dedicated resources)

      hbase.sn2.2xlarge

    • 16-core 64 GB (dedicated resources)

      hbase.sn2.4xlarge

    • 32-core 128 GB (dedicated resources)

      hbase.sn2.8xlarge

  • If you use local HDDs, you can select the local_hdd_pro type.
    • 16-core 64 GB (local disks and dedicated resources)

      hbase.d1.4xlarge

    • 24-core 96 GB (local disks and dedicated resources)

      hbase.d1.6xlarge

    • 32-core 128 GB (local disks and dedicated resources)

      hbase.d1.8xlarge

    • 40-core 176 GB (local disks and dedicated resources)

      hbase.d1.10xlarge

  • If you use local SSDs, you can select the local_ssd_pro type.
    • 4-core 32 GB (local SSDs)

      hbase.i2.xlarge

    • 8-core 64 GB (local SSDs)

      hbase.i2.2xlarge

    • 16-core 128 GB (local SSDs)

      hbase.i2.4xlarge

    • 32-core 256 GB (local SSDs)

      hbase.i2.8xlarge

ApsaraDB for HBase Performance-enhanced Edition
  • 4-core 16 GB (dedicated resources) hbase.sn2.large
  • 4-core 8 GB (dedicated resources) hbase.sn1.large
  • 8-core 16 GB (dedicated resources) hbase.sn1.2xlarge
  • 8-core 32 GB (dedicated resources) hbase.sn2.2xlarge
  • 16-core 32 GB (dedicated resources) hbase.sn1.4xlarge
  • 16-core 64 GB (dedicated resources) hbase.sn2.4xlarge

BDS

Engine Master node Core node
BDS You can enter an empty string.
  • 4-core 8 GB (dedicated resources) hbase.sn1.large
  • 8-core 16 GB (dedicated resources) hbase.sn1.2xlarge
  • 16-core 32 GB (dedicated resources) hbase.sn1.4xlarge
  • 32-core 128 GB (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. You can still use ApsaraDB for HBase in single-node mode that you purchased earlier.
  • To create an ApsaraDB for HBase instance in single-node mode, call the CreateCluster operation and set the NodeCount request parameter to 1.
  • If the ApsaraDB for HBase instance works in single-node mode, set the core_instance_quantity parameter to 1.
Engine Master node Core node
ApsaraDB for HBase in single-node mode You can enter an empty string.
  • 2-core 4 GB hbase.sn1ne.large
  • 4-core 8 GB hbase.sn1ne.xlarge