Updated on 2025-12-30 GMT+08:00

Buying a GeminiDB HBase Instance

This section describes how to buy a GeminiDB HBase instance.

GeminiDB Cassandra, DynamoDB-Compatible, and HBase instances of each tenant share a quota. Each tenant can create a maximum of 50 instances by default. To request a higher quota, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.

Prerequisites

Procedure

  1. Log in to the GeminiDB console.
  2. On the Instances page, click .
  3. On the displayed page, select a billing mode, set Compatible API to HBase, set other parameters, and click Next. If HBase is unavailable, contact the customer service.

    Figure 1 Billing mode and basic information (cloud native storage)
    Table 1 Billing mode

    Parameter

    Description

    Billing Mode

    Select Yearly/Monthly or Pay-per-use.

    • Yearly/Monthly
      • Specify Required Duration. The system deducts fees from your account based on the service price.
      • If you do not need such an instance any longer after it expires, change the billing mode to pay-per-use. For details, see Changing Yearly/Monthly to Pay-per-Use.
        NOTE:
    • Pay-per-use
      • You do not need to set Validity Period because you are billed based on how long you have actually used your instance.
      • To use an instance for a long time, change its billing mode to yearly/monthly to reduce costs. For details, see Changing Pay-per-Use to Yearly/Monthly.
    Table 2 Basic information

    Parameter

    Description

    Region

    Region where a tenant is located

    NOTE:

    To reduce network latency, select a region nearest from which you will access the instance. Instances deployed in different regions cannot communicate with each other over a private network. After you buy an instance, you cannot change its region.

    DB Instance Name

    The instance name:

    • Can be the same as an existing instance name.
    • Can include 4 to 64 bytes and must start with a letter. It is case-sensitive and allows only letters, digits, hyphens (-), and underscores (_).

    Compatible API

    HBase

    GeminiDB is compatible with mainstream NoSQL databases, including Redis, DynamoDB, Cassandra, and InfluxDB. You can select GeminiDB APIs by following How Do I Select an API?

    DB Instance Type

    Cluster

    One cluster consists of at least three nodes. A cluster is easy to scale out to meet increasing data growth needs. A cluster is recommended when dealing with stringent availability demands, substantial data volumes, and the need for seamless scalability.

    AZ

    An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network.

    Figure 2 Specifications and storage
    Table 3 Specifications and storage

    Parameter

    Description

    Instance Specifications

    Higher CPU specifications provide better performance. Select specifications as needed.

    Nodes

    Number of nodes that the instance is deployed on.

    If the number of nodes exceeds the upper limit, you can choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.

    After an instance is created, you can add nodes. For details, see Manually Adding Instance Nodes.

    Storage Space

    Instance storage space. The range depends on the instance specifications.

    To scale up storage, you need to add at least 1 GB each time. The value must be an integer.

    Auto Scale

    Whether autoscaling is enabled.

    You can enable Auto Scale after an instance is created. For details, see Automatically Scaling Up Storage Space.

    Table 4 Network configuration

    Parameter

    Description

    VPC

    A dedicated virtual network where your instance is located. It isolates networks for different workloads to enhance security.

    The system will assign a default VPC (default_vpc). You can also use an existing, new, or shared VPC.

    After an instance is created, the VPC cannot be changed.

    • Select an existing VPC of the current account from the drop-down list.
    • To use a new VPC, create a VPC first and then select it from the drop-down list.

      For details about how to create a VPC, see Creating a VPC in Virtual Private Cloud User Guide.

    NOTE:
    • To connect an instance to an ECS over a private network, ensure they are in the same VPC. If they are not, create a VPC peering connection between them.

    Subnet

    A subnet where your instance is created. The subnet provides dedicated and isolated networks, improving network security.

    NOTE:

    An IPv6 subnet cannot be associated with your instance. Select an IPv4 subnet.

    Security Group

    A security group controls access between instances and other services. Ensure that the security group you selected allows your client to access the instance.

    If no security group is available, the system creates one for you.

    Table 5 Database configuration

    Parameter

    Description

    Administrator

    Username of the administrator account. The default value is rwuser.

    Administrator Password

    Password of the administrator account. The password:

    • Can include 8 to 32 characters.
    • Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!#%^*-_=+?
    • Cannot contain @ or /
    • For security reasons, set a strong password. The system will verify the password strength.

    Keep your password secure. The system cannot retrieve it if it is lost.

    Confirm Password

    This password must be consistent with administrator password.

    Enterprise Project

    This parameter is provided for enterprise users.

    An enterprise project groups cloud resources, so you can manage resources and members by project. The default project is default.

    Select an enterprise project from the drop-down list. For more information about enterprise projects, see Enterprise Management User Guide.

    Parameter Template

    A parameter template contains the configuration values of a database engine. The parameters can be applied to one or more instances of the same type. After creating an instance, you can modify the parameter template.

    You can modify the instance parameters as required after the instance is created.

    Table 6 Tags

    Parameter

    Description

    Tags

    (Optional) Identifier of a GeminiDB HBase instance. Adding tags helps you better identify and manage your instance.

    A maximum of 20 tags can be added for each instance.

    A tag consists of a tag key and a tag value.

    • A tag key is mandatory if the instance will be tagged.

      Each tag key is unique for each instance. The value can contain a maximum of 128 characters, including digits, letters, underscores (_), periods (.), and hyphens (-).

    • A tag value is optional if the instance will be tagged.

      The value can be empty.

      The value can contain a maximum of 255 characters, including digits, letters, underscores (_), periods (.), and hyphens (-).

  4. On the displayed page, confirm instance details.

    • To modify the configurations, click Previous.
    • If no modification is required, read and agree to the service agreement and click Submit.

  5. On the Instances page, view and manage the created instance.

    • The instance status is displayed as Creating.
    • After the instance is created, its status becomes Available.

      You can click in the upper right corner to refresh the instance status.

    • An automated backup policy is enabled by default during instance creation. After the instance is created, a full backup is created.