diff --git a/docs/geminidb/umn/nosql_01_0006.html b/docs/geminidb/umn/nosql_01_0006.html index 4ae232d8..820c4b47 100644 --- a/docs/geminidb/umn/nosql_01_0006.html +++ b/docs/geminidb/umn/nosql_01_0006.html @@ -4,7 +4,7 @@

The DB instance specifications depend on the selected DB engine.

GeminiDB Cassandra Instance Specifications

-
Table 1 GeminiDB Cassandra cluster instance specifications

Flavor

+
@@ -20,7 +20,7 @@ - - - - - - - - - - - -
Table 1 GeminiDB Cassandra cluster instance specifications

Specification

vCPUs

32

24,000

+

96,000

geminidb.cassandra.2xlarge.8

@@ -29,7 +29,7 @@

64

48,000

+

96,000

geminidb.cassandra.4xlarge.8

@@ -41,15 +41,6 @@

96,000

geminidb.cassandra.6xlarge.8

-

24

-

192

-

144,000

-

geminidb.cassandra.8xlarge.8

32

@@ -59,15 +50,6 @@

192,000

geminidb.cassandra.12xlarge.8

-

48

-

384

-

288,000

-

geminidb.cassandra.15xlarge.8

60

diff --git a/docs/geminidb/umn/nosql_02_0005.html b/docs/geminidb/umn/nosql_02_0005.html index db6ab592..c8bc418a 100644 --- a/docs/geminidb/umn/nosql_02_0005.html +++ b/docs/geminidb/umn/nosql_02_0005.html @@ -3,14 +3,17 @@

Connecting to a GeminiDB Cassandra Instance Over Private Networks

Scenarios

This section uses the Linux operating system as an example to describe how to connect an ECS to a GeminiDB Cassandra instance over private networks.

-

Constraints

  • The DB instances must be in the same VPC subnet as the ECS.
  • The ECS must be allowed in a security group that has access to the DB instances.
    • If the security group that the target DB instance belongs to is the default security group, you do not need to configure security group rules.
    • If the security group that the target DB instance belongs to is not the default security group, check whether the security group rules allow the ECS to connect to the DB instance. For details, see section Configuring Security Group Rules.

      If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.

      +

      Constraints

      • The DB instances must be in the same VPC subnet as the ECS.
      • The ECS must be allowed in a security group that has access to the DB instances.
        • If the target DB instance belongs to the default security group, you do not need to configure security group rules.
        • If the security group that the target DB instance belongs to is not the default security group, check whether the security group rules allow the ECS to connect to the DB instance. For details, see section Configuring Security Group Rules.

          If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.

          If the security group rule does not allow the access from the ECS, you need to add an inbound rule to the security group.

      • The default port of the GeminiDB Cassandra instance is 8635.
      -

      Prerequisites

      • Create an ECS running Linux. For details, see "Creating ECSs" in ECS User Guide.
      • Obtain the Cassandra client installation package from the Cassandra official website.
      • Before using this tool, install the Python dependency package cassandra-driver 3.11.0 or later.
      +

      Prerequisites

      -

      Using the Cassandra Client Tool to Connect to a DB Instance

      1. Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
      2. Upload the Cassandra client installation package to ECS.
      3. Obtain the client tool cqlsh.
      4. Connect to the DB instance in the directory where the cqlsh tool is located.

        ./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>

        +

        Using the Cassandra Client Tool to Connect to a DB Instance

        1. Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
        2. Upload the Cassandra client installation package 3.11.3 to the ECS. If Wget fails to be downloaded, download it to your local PC and then upload it to the ECS.

          wget https://archive.apache.org/dist/cassandra/3.11.3/apache-cassandra-3.11.3-bin.tar.gz

          +

          tar -zxvf apache-cassandra-3.11.3-bin.tar.gz

          +

        3. Obtain the client tool cqlsh.

          cd apache-cassandra-3.11.3/bin

          +

        4. Connect to the DB instance in the directory where the cqlsh tool is located.

          ./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>

          Example:

          ./cqlsh 192.168.1.8 8635 -u rwuser

          • <DB_HOST> indicates the private IP address of the node to be connected. Obtain the value from the Private IP Address column in the node list on the Basic Information page.
          • <DB_PORT> indicates the port number. The default value is 8635 and cannot be changed.
          • <DB_USER> indicates the database account name. The default value is rwuser.
          diff --git a/docs/geminidb/umn/nosql_02_0009.html b/docs/geminidb/umn/nosql_02_0009.html index cea91c30..b045f6d5 100644 --- a/docs/geminidb/umn/nosql_02_0009.html +++ b/docs/geminidb/umn/nosql_02_0009.html @@ -4,9 +4,12 @@

          Scenarios

          You can use an ECS or local device to connect to a GeminiDB instance over a public network.

          This section describes how to use a Linux ECS to connect to a GeminiDB Cassandra instance over a public network.

          -

          Prerequisites

          • Bind an EIP to the GeminiDB Cassandra instance node and set security group rules.
          • Create an ECS running Linux. For details, see "Creating ECSs" in ECS User Guide.
          • Obtain the Cassandra client installation package from the Cassandra official website.
          • Before using this tool, install the Python dependency package cassandra-driver 3.11.0 or later.
          +

          Prerequisites

          -

          Connecting to a DB Instance Through a Cassandra Client

          1. Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
          2. Upload the Cassandra client installation package to ECS.
          3. Obtain the client tool cqlsh.
          4. Connect to the DB instance in the directory where the cqlsh tool is located.

            ./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>

            +

            Connecting to a DB Instance Through a Cassandra Client

            1. Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
            2. Upload the Cassandra client installation package 3.11.3 to the ECS. If Wget fails to be downloaded, download it to your local PC and then upload it to the ECS.

              wget https://archive.apache.org/dist/cassandra/3.11.3/apache-cassandra-3.11.3-bin.tar.gz

              +

              tar -zxvf apache-cassandra-3.11.3-bin.tar.gz

              +

            3. Obtain the client tool cqlsh.

              cd apache-cassandra-3.11.3/bin

              +

            4. Connect to the DB instance in the directory where the cqlsh tool is located.

              ./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>

              Example:

              ./cqlsh 192.168.1.8 8635 -u rwuser

              • <DB_HOST> indicates the EIP of the node to be connected. Obtain the value from the EIP column in the node list on the Basic Information page.
              • <DB_PORT> indicates the port number. The default value is 8635 and cannot be changed.
              • <DB_USER> indicates the database account name. The default value is rwuser.