All Products
Search
Document Center

ApsaraDB for HBase:Node specifications

Last Updated:Aug 29, 2024

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

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

  • 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.

    • 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

  • 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 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

  • If you use local HDDs, you can select the local_hdd_pro type.

    • 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

  • If you use local SSDs, you can select the local_ssd_pro type.

    • 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

Big DataHub Service (BDS)

Engine

Master node

Core node

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 not 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 cores, 4 GB memory hbase.sn1ne.large

  • 4 cores, 8 GB memory hbase.sn1ne.xlarge