diff --git a/docs/geminidb/umn/ALL_META.TXT.json b/docs/geminidb/umn/ALL_META.TXT.json index b10c680b0..c8bf3128f 100644 --- a/docs/geminidb/umn/ALL_META.TXT.json +++ b/docs/geminidb/umn/ALL_META.TXT.json @@ -47,7 +47,7 @@ "node_id":"nosql_01_0001.xml", "product_code":"nosql", "code":"3", - "des":"GeminiDB is a distributed database with decoupled compute and storage architecture. The compute clusters consist of multiple homogeneous nodes, and data is stored in a di", + "des":"GeminiDB is a distributed database store with decoupled storage and compute. Its compute cluster consists of multiple homogeneous nodes.Data is stored in a distributed sh", "doc_type":"usermanual", "kw":"System Architecture,Introduction,User Guide", "search_title":"", @@ -629,7 +629,7 @@ "code":"32", "des":"This section describes how to change the CPU or memory of your instance to suit your service requirements.Instances can be scaled up or down.Services will be interrupted ", "doc_type":"usermanual", - "kw":"Changing a DB Instance Class,DB Instance Management,User Guide", + "kw":"Changing the CPU and Memory of an Instance,DB Instance Management,User Guide", "search_title":"", "metedata":[ { @@ -639,7 +639,7 @@ "IsBot":"Yes;No" } ], - "title":"Changing a DB Instance Class", + "title":"Changing the CPU and Memory of an Instance", "githuburl":"" }, { diff --git a/docs/geminidb/umn/CLASS.TXT.json b/docs/geminidb/umn/CLASS.TXT.json index 1a50ed4e6..de8e406f9 100644 --- a/docs/geminidb/umn/CLASS.TXT.json +++ b/docs/geminidb/umn/CLASS.TXT.json @@ -18,7 +18,7 @@ "code":"2" }, { - "desc":"GeminiDB is a distributed database with decoupled compute and storage architecture. The compute clusters consist of multiple homogeneous nodes, and data is stored in a di", + "desc":"GeminiDB is a distributed database store with decoupled storage and compute. Its compute cluster consists of multiple homogeneous nodes.Data is stored in a distributed sh", "product_code":"nosql", "title":"System Architecture", "uri":"nosql_01_0001.html", @@ -281,7 +281,7 @@ { "desc":"This section describes how to change the CPU or memory of your instance to suit your service requirements.Instances can be scaled up or down.Services will be interrupted ", "product_code":"nosql", - "title":"Changing a DB Instance Class", + "title":"Changing the CPU and Memory of an Instance", "uri":"nosql_03_0026.html", "doc_type":"usermanual", "p_code":"26", diff --git a/docs/geminidb/umn/nosql_01_0001.html b/docs/geminidb/umn/nosql_01_0001.html index 0bb7462f1..d1af77ae6 100644 --- a/docs/geminidb/umn/nosql_01_0001.html +++ b/docs/geminidb/umn/nosql_01_0001.html @@ -1,7 +1,9 @@

System Architecture

-

GeminiDB is a distributed database with decoupled compute and storage architecture. The compute clusters consist of multiple homogeneous nodes, and data is stored in a distributed, shared storage pool. Compute and storage resources are decoupled from each other so they can be flexibly scaled in or out without having to migrate any data.

+

GeminiDB is a distributed database store with decoupled storage and compute. Its compute cluster consists of multiple homogeneous nodes.

+

Data is stored in a distributed shared storage pool.

+

Compute and storage resources are decoupled from each other so they can be flexibly scaled in or out without having to migrate any data.

diff --git a/docs/geminidb/umn/nosql_01_0010.html b/docs/geminidb/umn/nosql_01_0010.html index 58c20d353..52d0207d1 100644 --- a/docs/geminidb/umn/nosql_01_0010.html +++ b/docs/geminidb/umn/nosql_01_0010.html @@ -2,15 +2,15 @@

Typical Application Scenarios

IoT

GeminiDB is compatible with Cassandra APIs. It is designed for write-intensive scenarios, specifically applied in manufacturing, logistics, health care, real estate, energy production, and agriculture. It can process data sent by different types of sensors for further analysis.

-

Advantages:

+

Highlights

  • High Write Performance: GeminiDB provides higher write performance than other NoSQL services.
  • High Scalability: Compute nodes can be scaled in or out to flexibly cope with traffic surges or large writes loads at any time.

Internet

E-commerce and entertainment websites that include product catalogs, recommendations, and personalization engines use GeminiDB when they require fast reading and writing of data and high scalability. GeminiDB stores visitor activities, making it easy for analysis tools to access data fast and to generate recommendations.

-

Advantages:

+

Highlights

  • High Write Performance: GeminiDB provides higher write performance than other NoSQL services.
  • Big Data Analysis: GeminiDB can work with Spark to provide recommendations to your customers in real-time.

Finance

With Spark′s big data analysis capabilities, GeminiDB helps companies in the finance sector build risk control systems and mitigate fraud.

-

Advantages:

+

Highlights

Big Data Analysis: Spark and other big data processing technologies enable real-time fraud detection and prevention.

diff --git a/docs/geminidb/umn/nosql_02_0004.html b/docs/geminidb/umn/nosql_02_0004.html index 266e4729d..b4fcd58b2 100644 --- a/docs/geminidb/umn/nosql_02_0004.html +++ b/docs/geminidb/umn/nosql_02_0004.html @@ -2,7 +2,7 @@

Configuring Security Group Rules

Scenarios

The default security group rule allows all outgoing data packets. ECSs and GeminiDB instances in the same security group can access each other. After a security group is created, you can create different rules for that security group, which allows you to control access to the GeminiDB instances that in it.

-

The following describes how to configure security groups.

+

The following describes how to set security groups.

Precautions

  • If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.
  • If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance separately.
    • To allow access to a GeminiDB Cassandra instance, you need to configure an inbound rule for the security group that the instance nodes belong to.
    • By default, the security group allows all outbound data packets, so you do not need to configure a security rule for the ECS. If not all access from the ECS is allowed, you need to configure an outbound rule for the ECS.
diff --git a/docs/geminidb/umn/nosql_02_0005.html b/docs/geminidb/umn/nosql_02_0005.html index c8bc418ac..cb1fe3f72 100644 --- a/docs/geminidb/umn/nosql_02_0005.html +++ b/docs/geminidb/umn/nosql_02_0005.html @@ -8,7 +8,7 @@
  • The default port of the GeminiDB Cassandra instance is 8635.
    • -

    Prerequisites

    +

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

      diff --git a/docs/geminidb/umn/nosql_02_0009.html b/docs/geminidb/umn/nosql_02_0009.html index b045f6d5d..099ffddc7 100644 --- a/docs/geminidb/umn/nosql_02_0009.html +++ b/docs/geminidb/umn/nosql_02_0009.html @@ -4,7 +4,7 @@

      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

      +

      Prerequisites

      • Bind an EIP to the GeminiDB Cassandra instance node and set security group rules.
      • You have created an ECS running Linux. For details, see "Creating ECSs" in ECS User Guide.
      • You have obtained the Cassandra client installation package 3.11.3 from the official website.
      • If Python is not installed, download and install Python 2.7 and cassandra-driver 3.11.0 or later.

      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

        @@ -22,21 +22,21 @@
        • Run HELP <COMMAND> to query the usage of a command. Example: HELP DESC
        • Keyspace syntax
          • Create a keyspace. Example:

            CREATE KEYSPACE IF NOT EXISTS test_keyspace WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'};

            Set the keyspace name to test_keyspace, replication to SimpleStrategy, and number of replicas to 3.

          • Run DESC <keyspace_name> to verify the creation results.
          • Run use <keyspace_name> to switch to the keyspace you created.
          • Run DROP KEYSPACE <keyspace_name> to delete the keyspace you created.
          -
        • Table syntax
          • Create a table. Example:

            CREATE TABLE test_table(user_id int, age int, user_name text, PRIMARY KEY(user_id));

            +
          • Table syntax
            • Create a table, for example:

              CREATE TABLE test_table(user_id int, age int, user_name text, PRIMARY KEY(user_id));

              test_table is a table name defined by the following three columns: user_id, age, and user_name. user_id indicates a user ID of the INT data type. age indicates user age of the INT data type. user_name indicates a username of the TEXT data type. The primary key is user_id.

            • Run DESC <table_name> to verify the creation results.
            • Insert data into the table. Example:

              INSERT INTO test_table (user_id, age, user_name) VALUES (1, 10, 'user1');

              INSERT INTO test_table (user_id, age, user_name) VALUES (2, 20, 'user2');

              INSERT INTO test_table (user_id, age, user_name) VALUES (3, 30, 'user3');

              -
            • Run SELECT * FROM <table_name> to query table data.
            • Add a column to the table. Example:

              ALTER TABLE test_table ADD gender text;

              -
            • Update data in a table of a keyspace. Example:

              UPDATE test_keyspace.test_table SET prename = 'user_prename1' WHERE user_id = 1;

              +
            • Run SELECT * FROM <table_name> to query table data.
            • Add a column to the table, for example:

              ALTER TABLE test_table ADD gender text;

              +
            • Update data in a table of a keyspace, for example:

              UPDATE test_keyspace.test_table SET prename = 'user_prename1' WHERE user_id = 1;

              UPDATE test_keyspace.test_table SET prename = 'user_prename2' WHERE user_id = 2;

              UPDATE test_keyspace.test_table SET prename = 'user_prename3' WHERE user_id = 3;

              -
            • Delete data from a table in a keyspace. Example:

              Delete the age data of the user whose ID is 1.

              +
            • Delete data from a table in a keyspace, for example:

              Delete the age data of the user whose ID is 1.

              DELETE age FROM test_keyspace.test_table WHERE user_id=1;

              Delete the entire record of the user whose ID is 2.

              DELETE FROM test_keyspace.test_table WHERE user_id=2;

              -
            • Clear all records in the table. Example:

              TRUNCATE test_keyspace.test_table;

              -
            • Delete the entire table. Example:

              DROP TABLE test_keyspace.test_table;

              +
            • Clear all records in the table, for example:

              TRUNCATE test_keyspace.test_table;

              +
            • Delete an entire table, for example:

              DROP TABLE test_keyspace.test_table;

      diff --git a/docs/geminidb/umn/nosql_03_0002.html b/docs/geminidb/umn/nosql_03_0002.html index 2efcc4429..12cd49d86 100644 --- a/docs/geminidb/umn/nosql_03_0002.html +++ b/docs/geminidb/umn/nosql_03_0002.html @@ -14,7 +14,7 @@
    3. Configuring Auto Scale
      4. -
    4. Changing a DB Instance Class
      +
    5. Changing the CPU and Memory of an Instance
    6. Adding Nodes
      7. diff --git a/docs/geminidb/umn/nosql_03_0009.html b/docs/geminidb/umn/nosql_03_0009.html index 012cc824e..595f926bf 100644 --- a/docs/geminidb/umn/nosql_03_0009.html +++ b/docs/geminidb/umn/nosql_03_0009.html @@ -7,7 +7,7 @@
      1. On the Instance Management page, click the target DB instance.
      2. On the Backups & Restorations page, locate the target backup and click Restore.

      Method 2

      On the Backup Management page, locate the target backup and click Restore.

      -

    7. In the displayed dialog box, confirm the current instance details and restoration method and click OK.

      • The default API type and DB engine version are the same as those of the original instance and cannot be changed.
      • GeminiDB automatically calculates the minimum storage space required for restoration based on the size of the selected backup file. The storage space depends on the instance specifications, and must be a multiple of 10 GB.
      • You need to set a new administrator password.
      +

    8. In the displayed dialog box, confirm the current instance details and restoration method and click OK.

      • The default API type and DB engine version are the same as those of the original instance and cannot be changed.
      • GeminiDB automatically calculates the minimum storage space required for restoration based on the size of the selected backup file. The storage space depends on the instance specifications, and must be a multiple of 10 GB.
      • You need to set a new administrator password.
      • To modify other parameters, see the description of creating DB instances of other DB engines in the Getting Started.

    9. View the restoration results.

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      After the restoration, the system will perform a full backup.

      diff --git a/docs/geminidb/umn/nosql_03_0011.html b/docs/geminidb/umn/nosql_03_0011.html index bb156677b..0cf2da1ec 100644 --- a/docs/geminidb/umn/nosql_03_0011.html +++ b/docs/geminidb/umn/nosql_03_0011.html @@ -372,7 +372,7 @@

      P75 read latency

      Unit: ms

      -

      ≥ 0 ms

      +

      ≥ 0 ms

      Monitored object: database

      Monitored object: GeminiDB Cassandra instance node

      @@ -570,7 +570,7 @@

      ≥ 0 Counts

      Monitored object: database

      -

      Monitored object: node of the Kunpeng-based GeminiDB Cassandra instance

      +

      Monitored object: GeminiDB Cassandra instance node

      1 minute

      diff --git a/docs/geminidb/umn/nosql_03_0014.html b/docs/geminidb/umn/nosql_03_0014.html index bff1318e4..63c1b7125 100644 --- a/docs/geminidb/umn/nosql_03_0014.html +++ b/docs/geminidb/umn/nosql_03_0014.html @@ -5,7 +5,7 @@

      Adding tags to GeminiDB instances helps you better identify and manage them. An instance can be tagged during or after it is created.

      After an instance is tagged, you can search for the tag key or value to quickly query the instance details.

    -

    Precautions

    • You are advised to set predefined tags on the TMS console.
    • A tag consists of a key and value. You can add only one value for each key. For details about the naming rules of tag keys and tag values, see Table 1.
    • Up to 20 tags can be added for each instance.
    +

    Usage Notes

    • You are advised to set predefined tags on the TMS console.
    • A tag consists of a key and value. You can add only one value for each key. For details about the naming rules of tag keys and tag values, see Table 1.
    • Up to 20 tags can be added for each instance.
    @@ -33,14 +33,14 @@
    Table 1 Naming rules

    Parameter

    -

    Adding a Tag

    1. Log in to the GeminiDB console.
    2. On the Instances page, click the name of the target instance to go to the Basic Information page.
    3. In the navigation pane on the left, click Tags.
    4. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value, and click OK.
    5. View and manage tags on the Tags page.
    +

    Adding a Tag

    1. Log in to the GeminiDB console.
    2. On the Instances page, click the target instance. The Basic Information page is displayed.
    3. In the navigation pane on the left, click Tags.
    4. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value, and click OK.
    5. View and manage tags on the Tags page.
    -

    Editing a Tag

    1. Log in to the GeminiDB console.
    2. On the Instances page, click the name of the target instance to go to the Basic Information page.
    3. In the navigation pane on the left, click Tags.
    4. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

      Only the tag value can be edited when editing a tag.

      +

      Editing a Tag

      1. Log in to the GeminiDB console.
      2. On the Instances page, click the target instance. The Basic Information page is displayed.
      3. In the navigation pane on the left, click Tags.
      4. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

        Only the tag value can be edited when editing a tag.

      5. View and manage tags on the Tags page.
      -

      Deleting a Tag

      1. Log in to the GeminiDB console.
      2. On the Instances page, click the name of the target instance to go to the Basic Information page.
      3. In the navigation pane on the left, click Tags.
      4. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
      5. After a tag has been deleted, it will not be displayed on the Tags page.
      +

      Deleting a Tag

      1. Log in to the GeminiDB console.
      2. On the Instances page, click the target instance. The Basic Information page is displayed.
      3. In the navigation pane on the left, click Tags.
      4. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
      5. After a tag has been deleted, it will not be displayed on the Tags page.
      -

      Searching an Instance by Tag

      1. Log in to the GeminiDB console.
      2. On the Instances page, click Search by Tag in the upper right corner of the instance list.
      3. Enter the key or value of the tag to be queried and click Search to query the instance associated with the tag.
      +

      Searching an Instance by Tag

      1. Log in to the GeminiDB console.
      2. On the Instances page, click Search by Tag in the upper right corner of the instance list.
      3. Enter the key or value of the tag to be queried and click Search to query the instance associated with the tag.
      diff --git a/docs/geminidb/umn/nosql_03_0026.html b/docs/geminidb/umn/nosql_03_0026.html index 9eb716e03..0e80ad551 100644 --- a/docs/geminidb/umn/nosql_03_0026.html +++ b/docs/geminidb/umn/nosql_03_0026.html @@ -1,18 +1,18 @@ -

      Changing a DB Instance Class

      +

      Changing the CPU and Memory of an Instance

      Scenarios

      This section describes how to change the CPU or memory of your instance to suit your service requirements.

      -

      Precautions

      • Instances can be scaled up or down.
      • Services will be interrupted for 5 to 10 minutes when you change DB instance CPU or memory, so you are advised to perform these operations during off-peak hours.
      • You are not advised to perform DDL operations when changing the CPU and memory.

        A data definition language (DDL) is a syntax for defining data structures and database objects. Common examples of DDL statements include CREATE, ALTER, and DROP. DDL is used to create, modify, and delete database objects, such as tables, indexes, views, functions, stored procedures, and triggers.

        +

        Usage Notes

        • Instances can be scaled up or down.
        • Services will be interrupted for 5 to 10 minutes when you change DB instance CPU or memory, so you are advised to perform these operations during off-peak hours.
        • You are not advised to perform DDL operations when changing the CPU and memory.

          A data definition language (DDL) is a syntax for defining data structures and database objects. Common examples of DDL statements include CREATE, ALTER, and DROP. DDL is used to create, modify, and delete database objects, such as tables, indexes, views, functions, stored procedures, and triggers.

        -

        Procedure

        1. Log in to the GeminiDB console.
        2. On the Instances page, locate the target instance and click its name.
        3. In the in DB Information area on the Basic Information page, click Change next to the Specifications field.
        4. On the displayed page, select the desired vCPUs and memory and click Next.
        5. On the displayed page, confirm the specifications.

          • If you need to modify your settings, click Previous to go back to the page where you specify details.
          • If you do not need to modify your settings, click Submit.
          -

        6. View the DB instance class change result.

          Go to the Basic Information page and in the Specifications area you can see the new specifications.

          +

          Procedure

          1. Log in to the GeminiDB console.
          2. On the Instances page, click the target instance name.
          3. In the in DB Information area on the Basic Information page, click Change next to the Specifications field.
          4. On the displayed page, select the desired vCPUs and memory and click Next.
          5. On the displayed page, confirm the specifications.

            • If you need to modify your settings, click Previous to go back to the page where you specify details.
            • If you do not need to modify your settings, click Submit.
            +

          6. Check the change results.

            Go to the Basic Information page and in the Specifications area you can see the new specifications.

          -

          Method 2

          1. Log in to the GeminiDB console.
          2. On the Instances page, locate the instance whose specifications you want to change and choose Change Specifications in the Operation column.
          3. On the displayed page, select the desired vCPUs and memory and click Next.
          4. On the displayed page, confirm the specifications.

            • If you need to modify your settings, click Previous to go back to the page where you specify details.
            • If you do not need to modify your settings, click Submit.
            -

          5. View the DB instance class change result.

            Go to the Basic Information page and in the Specifications area you can see the new specifications.

            +

            Method 2

            1. Log in to the GeminiDB console.
            2. On the Instances page, locate the instance whose specifications you want to change and choose Change Specifications in the Operation column.
            3. On the displayed page, select the desired vCPUs and memory and click Next.
            4. On the displayed page, confirm the specifications.

              • If you need to modify your settings, click Previous to go back to the page where you specify details.
              • If you do not need to modify your settings, click Submit.
              +

            5. Check the change results.

              Go to the Basic Information page and in the Specifications area you can see the new specifications.

          diff --git a/docs/geminidb/umn/nosql_04_change_history.html b/docs/geminidb/umn/nosql_04_change_history.html index 1269496ae..f5530d103 100644 --- a/docs/geminidb/umn/nosql_04_change_history.html +++ b/docs/geminidb/umn/nosql_04_change_history.html @@ -2,16 +2,32 @@

          Change History

          -

          Released On

          +
          - - - + + + + + + + + +

          Released

          Description

          +

          Change History

          2024-04-30

          +

          2025-02-28

          This issue is the sixth official release.

          -

          GaussDB NoSQL is changed to GeminiDB.

          +

          This issue is the ninth official release.

          +

          2024-11-30

          +

          This issue is the eighth official release.

          +

          2024-08-30

          +

          This issue is the seventh official release, which incorporates the following change:

          +

          Added Configuring Auto Scale.

          +

          2024-04-30

          +

          This issue is the sixth official release, which incorporates the following change:

          +

          Changed GaussDB NoSQL to GeminiDB.

          2020-07-31

          diff --git a/docs/geminidb/umn/nosql_06_0003.html b/docs/geminidb/umn/nosql_06_0003.html index 2ba80d5e9..b7d0af635 100644 --- a/docs/geminidb/umn/nosql_06_0003.html +++ b/docs/geminidb/umn/nosql_06_0003.html @@ -2,7 +2,7 @@

          Creating a GeminiDB Cassandra Instance

          This section describes how to create a DB instance that is compatible with Cassandra APIs.

          -

          Procedure

          1. Log in to the GeminiDB console by following Logging In to the GeminiDB Console.
          2. On the Instances page, click Create DB Instance.
          3. On the displayed page, select your DB instance specifications and click Create Now.

            +

            Procedure

            1. Log in to the GeminiDB console.
            2. On the Instances page, click Create DB Instance.
            3. On the displayed page, select your DB instance specifications and click Create Now.

              @@ -154,7 +154,7 @@
              Table 1 Basic information

              Parameter

              Description

              @@ -55,8 +55,8 @@

              Instance Specifications

              The CPU and memory of a DB instance.

              -

              Different performance specifications support different numbers of connections and maximum IOPSs. Select CPU and memory specifications based on your service requirements.

              -

              After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

              +

              Performance specifications vary depending on the connections and maximum IOPS.

              +

              After a DB instance is created, you can change its CPU and memory. For details, see Changing the CPU and Memory of an Instance.

              Nodes

              @@ -69,10 +69,10 @@

              Storage space depends on the instance specifications. The minimum storage space is 10 GB, and the storage space you set must be an integer. You can select a minimum of 10 GB each time.

              After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.

              -

              When configuring storage space of a GeminiDB Cassandra instance, you are advised to enable autoscaling. Then set trigger conditions and limit of autoscaling. When trigger conditions are met, the system will scale up the storage to ensure that the instance keeps available.

              +

              When configuring storage space of a GeminiDB Cassandra instance, you are advised to enable autoscaling. Then set trigger conditions and limit of autoscaling. After autoscaling is triggered, the system automatically scales up the storage to ensure that the instance has sufficient storage and keeps available.

              Figure 1 Auto Scale

              Pay attention to the following parameters:

              -
              • Trigger If Available Storage Drops To: storage threshold for triggering autoscaling. When the available storage usage drops to this value or the available storage space drops to 10 GB, autoscaling is triggered.
              • Increase By: percentage that your instance storage will be scaled up at. If the increased storage is not a multiple of 10 GB, the system will round it up to the nearest multiple of 10 GB. At least 100 GB is added each time.
              • Storage Limit: maximum amount that the system can automatically scale up an instance's storage space to. The value must be no less than the current storage of your instance and cannot exceed the storage space upper limit defined by your instance specifications.
              +
              • Trigger If Available Storage Drops To: storage threshold for triggering autoscaling. When the available storage usage drops to this value or the available storage space drops to 10 GB, autoscaling is triggered.
              • Increase By: percentage that your instance storage will be scaled up at. If the increased storage is not a multiple of 10 GB, the system will round it up to the nearest multiple of 10 GB. At least 100 GB is added each time.
              • Storage Limit: maximum amount that the system can automatically scale up an instance's storage space to. The value must be no less than the current storage of your instance and cannot exceed the storage space upper limit defined by your instance specifications.
              NOTE:
              • Once autoscaling is enabled, an agency will be created and fees will be automatically deducted.
              • You can enable autoscaling after an instance is created. For details, see Configuring Auto Scale.

              The setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for each instance.

              A tag is composed of a key-value pair.

              -
              • Key: Mandatory if the DB instance is going to be tagged

                Each tag key must be unique for each DB instance. The key can include up to 36 characters, including digits, letters, underscores (_), and hyphens (-).

                +
                • Key: Mandatory if the DB instance is going to be tagged

                  Each tag key is unique for each instance. The key can include up to 36 characters, including digits, letters, underscores (_), and hyphens (-).

                • Value: Optional if the DB instance is going to be tagged

                  The value can contain up to 43 characters, including digits, letters, underscores (_), periods (.), and hyphens (-).

                After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Managing Tags.

                diff --git a/docs/geminidb/umn/nosql_increase_storage1.html b/docs/geminidb/umn/nosql_increase_storage1.html index a243d5e24..82563d3b3 100644 --- a/docs/geminidb/umn/nosql_increase_storage1.html +++ b/docs/geminidb/umn/nosql_increase_storage1.html @@ -32,9 +32,9 @@
                • -

                Precautions

                • The instance is in the Available status.
                • Once autoscaling is enabled, an agency will be created and fees will be automatically deducted.
                +

                Usage Notes

                • The instance is in the Available status.
                • Once autoscaling is enabled, an agency will be created and fees will be automatically deducted.
                -

                Automatically Scaling Up Storage of a Single Instance

                1. Log in to the GeminiDB console by following Logging In to the GeminiDB Console.
                2. On the Instances page, click the instance. The Basic Information page is displayed.
                3. In the Storage Space area, click Auto Scale.

                  Figure 1 Auto Scale
                  +

                  Automatically Scaling Up Storage of a Single Instance

                  1. Log in to the GeminiDB console.
                  2. On the Instances page, click the target instance. The Basic Information page is displayed.
                  3. In the Storage Space area, click Auto Scale.

                    Figure 1 Auto Scale

                  4. Toggle on Auto Scale and specify the parameters below.

                    Figure 2 Configuring autoscaling
                    Table 1 Parameter description

                    Parameter

                    @@ -69,7 +69,7 @@

                  5. Click OK.
                    6. -

                    Automatically Scaling Up Storage of Multiple Instances In Batches

                    1. Log in to the GeminiDB console by following Logging In to the GeminiDB Console.
                    2. Select instances and click Auto Scale.

                      Figure 3 Auto Scale
                      +

                      Automatically Scaling Up Storage of Multiple Instances In Batches

                      1. Log in to the GeminiDB console.
                      2. Select instances and click Auto Scale.

                        Figure 3 Auto Scale

                      3. Select an instance, toggle on Auto Scale, and specify the parameters below.

                        Figure 4 Batch Auto Scale
                        -
                        Table 2 Parameter description

                        Parameter

                        @@ -90,7 +90,7 @@

                        Increase By

                        Percentage of the current storage to be automatically scaled. The value can be 10, 15, or 20. If the value is not a multiple of 10, the value is rounded up. At least 100 GB is added each time.

                        +

                        Percentage of the current storage to be automatically scaled. The value can be 10, 15, or 20. If the value is not a multiple of 10, the value is rounded up. At least 100 GB is added each time.

                        Storage Limit