Help Center/ GeminiDB/ GeminiDB Redis API/ Getting Started with GeminiDB Redis API/ Buying and Connecting to a Cluster Instance
Updated on 2024-10-11 GMT+08:00

Buying and Connecting to a Cluster Instance

This section describes how to buy a GeminiDB Redis cluster instance on the GeminiDB console and connect to the instance.

With a sharded cluster architecture, this type of instance supports connections through proxies and is compatible with Redis clusters. It offers strong horizontal expansion capability, supporting millions of QPS and dozens of TB-level services.

Each tenant has up to 50 GeminiDB Redis instances by default. To request a higher quota, contact customer service.

Step 1: Buying an Instance

  1. Log in to the GeminiDB console.
  2. In the service list, choose Databases > GeminiDB.
  3. On the Instances page, click Buy DB Instance.
  4. On the displayed page, select a billing mode, configure instance specifications, and click Next.

The following parameters are for reference only. Select proper specifications as needed. Table 1 lists details about the parameters.

  • Billing Mode: Select Pay-per-use.
  • Region: Select EU-Dublin.
  • DB Instance Name: Enter a custom name.
  • Compatible API: Select Redis.
  • DB Instance Type: Select Cluster.
  • Compatible Version: Select 6.2.
  • CPU Type: Select x86 (default).
  • AZ: Select cn-north-4a,cn-north-4b,cn-north-4c.
  • Instance Creation Mode: Select Fast configure.
  • Instance Specifications: Select 8 GB and Standard 1 vCPU.
  • Network information: Configure VPC, subnet, and Database Port (default)
  • Database Password: Enter a value based on the password policy.
  • Enterprise Project: Select default.
  • Retain the default values for other parameters.
    Figure 1 Billing mode and basic information
    Figure 2 Specifications and storage

    5. On the order confirmation page, check the instance information. If you need to modify the information, click Previous. If no modification is required, read and agree to the service agreement and click Submit.

    6. Click Back to Instance Management to go to the instance list.

    7. On the Instances page, view and manage the created instance.
    • Creating an instance takes about 5 to 9 minutes. During the process, the instance status becomes Creating.
    • After the creation is complete, the status changes to Available.
    Figure 3 Successful purchase

Step 2: Connecting to an Instance Through DAS

DAS enables you to manage DB instances from a web-based console, simplifying database management and improving efficiency. You can connect and manage instances through DAS. By default, you have permission of remote login. DAS is secure and convenient for connecting to DB instances.

  1. Log in to the GeminiDB console.
  2. In the service list, choose Databases > GeminiDB.
  3. In the instance list, locate the target instance and click Log In in the Operation column.
    Figure 4 Connecting to a GeminiDB Redis instance

    Alternatively, click the instance name to go to the Basic Information page. Click Log In in the upper right corner of the page.

    Figure 5 Connecting to a GeminiDB Redis instance
  4. Enter the password for logging in to the instance.

    You need to enter the password only when you log in to a GeminiDB Redis instance first time or after you reset the password.

    Figure 6 Logging in to the GeminiDB Redis instance
  5. Manage relevant databases.
    Figure 7 Instance homepage
    • Save commands to the execution record.

      This function is enabled by default to save the recently executed commands for your later query.

      Then you can click the Executed Commands tab on the lower page to view historical commands.

      Figure 8 Viewing executed commands

      If this function is disabled, the commands executed subsequently are not displayed. You can click next to Save Executed SQL Statements in the upper right corner to disable this function.

    • Execute a command.

      Enter a command in the command window and click Execute or F8.

      • Do not use transactions, Lua scripts, Pub/Sub commands, or other commands that have blocking semantics.
      • For an instance that supports multiple databases, you can change the current database on the console but cannot change it using a SELECT statement.
      Figure 9 Executing a command

      After a command is executed, you can view the execution result on the Results page.

    • Save a command.

      You can save a command to all instances, the current instance, or the current database. Then you can view details in My Commands.

      Figure 10 Saving a command
    • View my commands.

      Common commands are displayed the My Commands page.

      You can set a filter to narrow the scope of commands. If you select All, all commands saved in the current account are displayed.

      Figure 11 Filtering commands

      Alternatively, you can enter a command title or statement in the search box to search for the corresponding command.

      Figure 12 Searching for a command

      On the My Commands page, you can also create, edit, and delete a command or copy it to the Execute window.

      Figure 13 Managing a command

    • Clear a command.

      You can also press F10 to clear the command in the execution window.

      Figure 14 Clearing a command