Concepts
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
-- A region is a physical data center. Each region is completely independent, improving fault tolerance and stability. After a resource is created, its region cannot be changed.
- An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.
Concepts
The combination of a region and an availability zone (AZ) identifies the location of a data center. You can create resources in a specific AZ in a region.
+- Regions are defined by their geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region. Regions are classified as universal regions and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides only services of the same type or provides services only for specific tenants.
- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through the internal network. The fault of an AZ will not affect other AZs. The internal network provides economical connection with low latency.
- Instance Connection Methods
+ - Creating a GeminiDB Cassandra Instance
+ - Connecting to a GeminiDB Cassandra Instance Over Private Networks
- Connecting to a GeminiDB Cassandra Instance Over Public Networks
diff --git a/docs/geminidb/umn/nosql_02_0002.html b/docs/geminidb/umn/nosql_02_0002.html deleted file mode 100644 index f4d0a982..00000000 --- a/docs/geminidb/umn/nosql_02_0002.html +++ /dev/null @@ -1,174 +0,0 @@ - - -Creating a GeminiDB Cassandra Instance
--This section describes how to create a DB instance that is compatible with Cassandra APIs.
--Procedure
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click Create DB Instance.
- On the displayed page, select your DB instance specifications, and click Create Now.
-
- -
-Table 1 Basic information Parameter
-Description
-Region
-The region where the tenant is located.
-NOTICE:-Select the region nearest where you will be accessing the DB from so latency can be kept to a minimum and response time will be faster. Also, products deployed in different regions cannot communicate with each other through a private network and you cannot change the region of an instance after creating the instance.
-DB Instance Name
-The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
- - -After the DB instance is created, you can change the DB instance name. For details, see section Changing a DB Instance Name.
-Compatible API
-Cassandra
-DB Instance Type
-Cluster
-DB Engine Version
-3.11
-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 connection.
-- -
-Table 2 Specifications and storage Parameter
-Description
-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.
-Nodes
-The number of nodes ranges from 3 to 200. Select the number of nodes based on the site requirements.
-After a DB instance is created, you can add nodes. For details, see Adding Nodes.
-Storage Space
-Storage space depends on the instance specifications. The minimum storage space is 100 GB, and the storage space you set must be an integer. You can select a minimum of 1 GB each time you scale up storage space.
-After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.
-- -
-Table 3 Network Parameter
-Description
-VPC
-The virtual network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC.
-If there are no VPCs available, the system allocates resources to you by default.
-For details on how to create a subnet, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.
-NOTE:-After the GeminiDB Cassandra instance is created, the VPC where the instance resides cannot be changed.
- -Subnet
-A subnet provides dedicated network resources that are logically isolated from other networks for network security.
-Security Group
-A security group controls access between GeminiDB instances and other services. When you select a security group, you must ensure that it allows the client to access DB instances.
-If there are no security groups available, the system allocates resources to you by default.
-- -
-Table 4 Database configuration Parameter
-Description
-Administrator
-The default administrator account is rwuser.
-Administrator Password
-Set a password for the administrator. The password:
-- Must be 8 to 32 characters long.
- Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
- For security reasons, you must select a strong password. The system will verify the password strength.
Keep this password secure. If you lose it, the system cannot retrieve it.
-Confirm Password
-Enter the administrator password again.
-Parameter Template
-A parameter template contains engine configuration values that can be applied to one or more instances.
-After a DB instance is created, you can modify parameters to better meet your service requirements. For details, see Modifying a Parameter Template.
--
-Table 5 Tags Parameter
-Description
-Tags
-The setting is optional. Adding tags helps you better identify and manage your DB instances. Each DB instance can have up to 20 tags.
-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 (-).
- - 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.
- - On the displayed page, confirm the DB instance details.
- If you need to modify the specifications, click Previous to return to the previous page.
- If you do not need to modify the specifications, click Submit to start creating the instance.
- On the Instance Management page, view and manage your DB instances.
- Creating a DB instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
- After the creation is complete, the status changes to Available.
You can click
-
in the upper right corner of the page to refresh the DB instance statuses. - During creation, an automated backup policy is enabled by default. A full backup is automatically triggered after a DB instance is created.
-- diff --git a/docs/geminidb/umn/nosql_02_0004.html b/docs/geminidb/umn/nosql_02_0004.html index b8087185..266e4729 100644 --- a/docs/geminidb/umn/nosql_02_0004.html +++ b/docs/geminidb/umn/nosql_02_0004.html @@ -2,9 +2,9 @@- --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 set security groups.
+The following describes how to configure 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 the 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 68d57109..db6ab592 100644 --- a/docs/geminidb/umn/nosql_02_0005.html +++ b/docs/geminidb/umn/nosql_02_0005.html @@ -1,6 +1,6 @@ -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.
- By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.
Connecting to a GeminiDB Cassandra Instance Over Private Networks
+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.
@@ -8,7 +8,7 @@
- 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
- 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.
Using the Cassandra Client Tool to Connect to a DB Instance
- Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
- Upload the Cassandra client installation package to ECS.
- Obtain the client tool cqlsh.
- Connect to the DB instance in the directory where the cqlsh tool is located.
./cqlsh <DB_HOST> <DB_PORT> -u <DB_USER>
Example:
@@ -20,24 +20,24 @@
diff --git a/docs/geminidb/umn/nosql_02_0006.html b/docs/geminidb/umn/nosql_02_0006.html index 72259833..5f5c7b00 100644 --- a/docs/geminidb/umn/nosql_02_0006.html +++ b/docs/geminidb/umn/nosql_02_0006.html @@ -4,8 +4,6 @@Follow-up Operations
After logging in to the GeminiDB Cassandra instance, you can perform the following operations:
- Run the HELP command to view all supported commands.
- HELP <COMMAND>: This command queries the usage of a command. Example: HELP DESC
- Keyspace syntax
- Create a keyspace. Example:
CREATE KEYSPACE IF NOT EXISTS nosql WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'};
-Set the keyspace name to nosql, replication to SimpleStrategy, and number of replicas to 3.
+- HELP <COMMAND>: This command queries the usage of a command. Example: HELP DESC
- Keyspace syntax
- Create a keyspace, for 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.
- DESC <keyspace_name>: This command verifies the creation result.
- use <keyspace_name>: This command switches to the keyspace you created.
- DROP KEYSPACE <keyspace_name>: This command deletes the keyspace you created.
- Create a keyspace, for example:
- Table syntax
- Create a table. Example:
CREATE TABLE nosql_table(user_id int, age int, user_name text, PRIMARY KEY(user_id));
-The table name is nosql_table, and the following three columns are defined: user_id, age, and user_name. user_id is of the int type and indicates the user ID. age is of the int type and indicates the age of a user. user_name is of the text type and indicates the user name. The primary key is user_id.
- - DESC <table_name>: This command verifies the creation result.
- Insert data into the table. Example:
INSERT INTO nosql_table (user_id, age, user_name) VALUES (1, 10, 'user1');
-INSERT INTO nosql_table (user_id, age, user_name) VALUES (2, 20, 'user2');
-INSERT INTO nosql_table (user_id, age, user_name) VALUES (3, 30, 'user3');
- - SELECT * FROM <table_name>: This command queries table data.
- Add a column to the table. Example -
- Insert data to the added column. Example:
UPDATE nosql.nosql_table SET prename = 'user_prename1' WHERE user_id = 1;
-UPDATE nosql.nosql_table SET prename = 'user_prename2' WHERE user_id = 2;
-UPDATE nosql.nosql_table SET prename = 'user_prename3' WHERE user_id = 3;
- - Delete data in a keyspace. Example:
Delete the age data of the user whose ID is 1.
-DELETE age FROM nosql.nosql_table WHERE user_id=1;
+ - 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.
+ - DESC <table_name>: This command verifies the creation result.
- Insert data into the table, for 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');
+ - SELECT * FROM <table_name>: This command queries table data.
- Add a column to the table, for example: +
- 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, 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 nosql.nosql_table WHERE user_id=2;
- - Clear all records in the table. Example: -
- Delete the entire table. Example:
+
DELETE FROM test_keyspace.test_table WHERE user_id=2;
+ - Clear all records in the table, for example: +
- Delete an entire table, for example:
- Create a table, for example:
- Create a table. Example:
- Create a keyspace. Example:
-
-
- Creating a GeminiDB Cassandra Instance
- - Configuring Security Group Rules
- Connecting to a GeminiDB Cassandra Instance Over Private Networks
diff --git a/docs/geminidb/umn/nosql_02_0007.html b/docs/geminidb/umn/nosql_02_0007.html index d2b3c6c6..ec65f245 100644 --- a/docs/geminidb/umn/nosql_02_0007.html +++ b/docs/geminidb/umn/nosql_02_0007.html @@ -4,8 +4,6 @@-
-
- Creating a GeminiDB Cassandra Instance
- - Binding an EIP
- Configuring Security Group Rules
diff --git a/docs/geminidb/umn/nosql_02_0008.html b/docs/geminidb/umn/nosql_02_0008.html index c893f239..916f7ee2 100644 --- a/docs/geminidb/umn/nosql_02_0008.html +++ b/docs/geminidb/umn/nosql_02_0008.html @@ -1,14 +1,14 @@Binding an EIP
-Scenarios
The Elastic IP service provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Cassandra instance, you can bind an EIP to it to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB instance.
+Scenarios
The Elastic IP service provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Cassandra instance, you can bind an EIP to it to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB instance.
-Precautions
- Before accessing a database, you need to apply for an EIP on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see section Configuring Security Group Rules.
- To change the EIP that has been bound to a node, you need to unbind it from the node first.
Binding an EIP
- On the Instance Management page, click the target GeminiDB Cassandra instance.
- On the Basic Information page, in the Node Information area, locate the target node and click Bind EIP in the Operation column.
- In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
- In the EIP column, view the EIP that is successfully bound.
To unbind the EIP from the DB instance, see Unbinding an EIP.
+-Binding an EIP
- On the Instances page, click the target GeminiDB Cassandra instance.
- On the Basic Information page, in the Node Information area, locate the target node and click Bind EIP in the Operation column.
- In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
- In the EIP column, view the EIP that is successfully bound.
To unbind the EIP from the DB instance, see Unbinding an EIP.
diff --git a/docs/geminidb/umn/nosql_02_0009.html b/docs/geminidb/umn/nosql_02_0009.html index eec1eed6..4e3faa34 100644 --- a/docs/geminidb/umn/nosql_02_0009.html +++ b/docs/geminidb/umn/nosql_02_0009.html @@ -4,9 +4,9 @@Unbinding an EIP
- On the Instance Management page, click the target GeminiDB Cassandra instance.
- On the Basic Information page, in the Node Information area, locate the target node and click Unbind EIP in the Operation column.
- In the displayed dialog box, click Yes.
To bind an EIP to the DB instance again, see Binding an EIP.
+Unbinding an EIP
- On the Instances page, click the target GeminiDB Cassandra instance.
- On the Basic Information page, in the Node Information area, locate the target node and click Unbind EIP in the Operation column.
- In the displayed dialog box, click Yes.
To bind an EIP to the DB instance again, see Binding an EIP.
-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
- 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.
Connecting to a DB Instance Through a Cassandra Client
- Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
- Upload the Cassandra client installation package to ECS.
- Obtain the client tool cqlsh.
- 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
- Log in to the ECS. For details, see the section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
- Upload the Cassandra client installation package to ECS.
- Obtain the client tool cqlsh.
- 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.
- Check the connection result. If the following information is displayed, the connection is successful.
rwuser@cqlsh>
Follow-up Operations
After logging in to the GeminiDB Cassandra instance, you can perform the following operations:
-- Run the HELP command to view all supported commands.
- HELP <COMMAND>: This command queries the usage of a command. Example: HELP DESC
- Keyspace syntax
- Create a keyspace. Example:
CREATE KEYSPACE IF NOT EXISTS nosql WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'};
-Set the keyspace name to nosql, replication to SimpleStrategy, and number of replicas to 3.
- - DESC <keyspace_name>: This command verifies the creation result.
- use <keyspace_name>: This command switches to the keyspace you created.
- DROP KEYSPACE <keyspace_name>: This command deletes the keyspace you created.
Follow-up Operations
After logging in to the GeminiDB Cassandra instance, you can perform the following operations:
+- Run the HELP command to view all supported commands.
- Run HELP <COMMAND> to query the usage of a command. Example: HELP DESC
- Keyspace syntax
- Create a keyspace. Example:
CREATE KEYSPACE IF NOT EXISTS nosql WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'};
+Set the keyspace name to nosql, replication to SimpleStrategy, and replication_factor 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.
- Create a keyspace. Example:
- Table syntax
- Create a table. Example:
CREATE TABLE nosql_table(user_id int, age int, user_name text, PRIMARY KEY(user_id));
-The table name is nosql_table, and the following three columns are defined: user_id, age, and user_name. user_id is of the int type and indicates the user ID. age is of the int type and indicates the age of a user. user_name is of the text type and indicates the user name. The primary key is user_id.
- - DESC <table_name>: This command verifies the creation result.
- Insert data into the table. Example:
INSERT INTO nosql_table (user_id, age, user_name) VALUES (1, 10, 'user1');
+nosql_table indicates the table name, and the following three columns are defined: user_id, age, and user_name. user_id is the user ID of the INT type. age is the user age of the INT type. user_name is the username of the TEXT type. The primary key is user_id.
+ - Run DESC <table_name> to verify the creation results.
- Insert data into the table. Example:
INSERT INTO nosql_table (user_id, age, user_name) VALUES (1, 10, 'user1');
INSERT INTO nosql_table (user_id, age, user_name) VALUES (2, 20, 'user2');
INSERT INTO nosql_table (user_id, age, user_name) VALUES (3, 30, 'user3');
- - SELECT * FROM <table_name>: This command queries table data.
- Add a column to the table. Example -
- Insert data to the added column. Example:
UPDATE nosql.nosql_table SET prename = 'user_prename1' WHERE user_id = 1;
+ - Run SELECT * FROM <table_name> to query table data.
- Add a column to the table. Example: +
- Update data in a table of a keyspace. Example:
UPDATE nosql.nosql_table SET prename = 'user_prename1' WHERE user_id = 1;
UPDATE nosql.nosql_table SET prename = 'user_prename2' WHERE user_id = 2;
UPDATE nosql.nosql_table SET prename = 'user_prename3' WHERE user_id = 3;
- - Delete data in a keyspace. Example: +
- Delete data from a table in a keyspace. Example:
Delete the age data of the user whose ID is 1.
DELETE age FROM nosql.nosql_table WHERE user_id=1;
-Delete the entire record of the user whose ID is 2.
+Delete the entire record of the user whose ID is 2.
DELETE FROM nosql.nosql_table WHERE user_id=2;
- Clear all records in the table. Example:
- Delete the entire table. Example:
diff --git a/docs/geminidb/umn/nosql_02_0010.html b/docs/geminidb/umn/nosql_02_0010.html
deleted file mode 100644
index 21fef7a5..00000000
--- a/docs/geminidb/umn/nosql_02_0010.html
+++ /dev/null
@@ -1,174 +0,0 @@
-
-
-
Creating a GeminiDB Cassandra Instance
--This section describes how to create a DB instance that is compatible with Cassandra APIs.
--Procedure
- Log in to the GeminiDB console.
- On the Instance Management page, click Create DB Instance.
- On the displayed page, select your DB instance specifications and click Create Now.
-
- -
-Table 1 Basic information Parameter
-Description
-Region
-The region where the tenant is located.
-NOTICE:-Select the region nearest where you will be accessing the DB from so latency can be kept to a minimum and response time will be faster. Also, products deployed in different regions cannot communicate with each other through a private network and you cannot change the region of an instance after creating the instance.
-DB Instance Name
-The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
- - -After the DB instance is created, you can change the DB instance name. For details, see section Changing a DB Instance Name.
-Compatible API
-Cassandra
-DB Instance Type
-Cluster
-DB Engine Version
-3.11
-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 connection.
-- -
-Table 2 Specifications and storage Parameter
-Description
-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.
-Nodes
-The number of nodes ranges from 3 to 200. Select the number of nodes based on the site requirements.
-After a DB instance is created, you can add nodes. For details, see Adding Nodes.
-Storage Space
-Storage space depends on the instance specifications. The minimum storage space is 100 GB, and the storage space you set must be an integer. You can select a minimum of 1 GB each time you scale up storage space.
-After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.
-- -
-Table 3 Network Parameter
-Description
-VPC
-The virtual network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC.
-If there are no VPCs available, the system allocates resources to you by default.
-For details on how to create a subnet, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.
-NOTE:-After the GeminiDB Cassandra instance is created, the VPC where the instance resides cannot be changed.
- -Subnet
-A subnet provides dedicated network resources that are logically isolated from other networks for network security.
-Security Group
-A security group controls access between GeminiDB instances and other services. When you select a security group, you must ensure that it allows the client to access DB instances.
-If there are no security groups available, the system allocates resources to you by default.
-- -
-Table 4 Database configuration Parameter
-Description
-Administrator
-The default administrator account is rwuser.
-Administrator Password
-Set a password for the administrator. The password:
-- Must be 8 to 32 characters long.
- Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
- For security reasons, you must select a strong password. The system will verify the password strength.
Keep this password secure. If you lose it, the system cannot retrieve it.
-Confirm Password
-Enter the administrator password again.
-Parameter Template
-A parameter template contains engine configuration values that can be applied to one or more instances.
-After a DB instance is created, you can modify parameters to better meet your service requirements. For details, see Modifying a Parameter Template.
-- - On the displayed page, confirm the DB instance details.
- If you need to modify the specifications, click Previous to return to the previous page.
- If you do not need to modify the specifications, click Submit to start creating the instance.
- On the Instance Management page, view and manage your DB instances.
- Creating a DB instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
- After the creation is complete, the status changes to Available.
You can click
- in the upper right corner of the page to refresh the DB instance statuses. - During creation, an automated backup policy is enabled by default. A full backup is automatically triggered after a DB instance is created.
-- diff --git a/docs/geminidb/umn/nosql_02_0011.html b/docs/geminidb/umn/nosql_02_0011.html index 498da5ef..5294eebe 100644 --- a/docs/geminidb/umn/nosql_02_0011.html +++ b/docs/geminidb/umn/nosql_02_0011.html @@ -6,7 +6,7 @@- --
- Create a table. Example:
-Precautions
- By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.
- To access a GeminiDB Cassandra instance from resources outside the security group, you need to configure an inbound rule to allow access to the GeminiDB Cassandra instance.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select a region and a project. - Click Service List. Under Network, click Virtual Private Cloud.
- In the navigation pane on the left, choose .
- On the Security Groups page, click the security group name.
- On the Inbound Rules tab, click Add Rule. In the displayed Add Inbound Rule dialog box, set required parameters to add inbound rules. On the Outbound Rules tab, click Add Rule. In the displayed Add Outbound Rule dialog box, set required parameters to add outbound rules.
- In the displayed dialog box, set required parameters.
- Click OK.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Network, click Virtual Private Cloud.
- In the navigation pane on the left, choose .
- On the Security Groups page, click the security group name.
- On the Inbound Rules tab, click Add Rule. In the displayed Add Inbound Rule dialog box, set required parameters to add inbound rules. On the Outbound Rules tab, click Add Rule. In the displayed Add Outbound Rule dialog box, set required parameters to add outbound rules.
- In the displayed dialog box, set required parameters.
- Click OK.
diff --git a/docs/geminidb/umn/nosql_03_0002.html b/docs/geminidb/umn/nosql_03_0002.html index 193a045d..2efcc442 100644 --- a/docs/geminidb/umn/nosql_03_0002.html +++ b/docs/geminidb/umn/nosql_03_0002.html @@ -12,6 +12,8 @@- Scaling Up Storage Space
+
- Configuring Auto Scale
+- Changing a DB Instance Class
- Adding Nodes
diff --git a/docs/geminidb/umn/nosql_03_0003.html b/docs/geminidb/umn/nosql_03_0003.html index 2160119d..cf5bb211 100644 --- a/docs/geminidb/umn/nosql_03_0003.html +++ b/docs/geminidb/umn/nosql_03_0003.html @@ -5,7 +5,7 @@-Precautions
- If the instance status is Available, Abnormal, or Checking restoration, you can restart the instance.
- Restarting a DB instance interrupts services, so exercise caution when performing this operation.
- If you restart a DB instance, all nodes in the instance are also restarted.
diff --git a/docs/geminidb/umn/nosql_03_0004.html b/docs/geminidb/umn/nosql_03_0004.html index 32eb7c86..c560040e 100644 --- a/docs/geminidb/umn/nosql_03_0004.html +++ b/docs/geminidb/umn/nosql_03_0004.html @@ -5,7 +5,7 @@Procedure
- Log in to the GeminiDB console.
- On the Instance Management page, locate the DB instance you wish to restart and choose More > Restart in the Operation column.
Alternatively, click the DB instance you wish to restart, and on the displayed Basic Information page, click Restart in the upper right corner of the page.
+Procedure
- Log in to the GeminiDB console.
- On the Instances page, locate the DB instance you wish to restart and choose More > Restart in the Operation column.
Alternatively, click the DB instance you wish to restart, and on the displayed Basic Information page, click Restart in the upper right corner of the page.
- In the displayed dialog box, click Yes.
- Create a keyspace. Example:
-Precautions
Deleted nodes cannot be recovered. Exercise caution when performing this operation.
diff --git a/docs/geminidb/umn/nosql_03_0005.html b/docs/geminidb/umn/nosql_03_0005.html index a21c8dac..bb6de61c 100644 --- a/docs/geminidb/umn/nosql_03_0005.html +++ b/docs/geminidb/umn/nosql_03_0005.html @@ -5,7 +5,7 @@Procedure
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the instance whose nodes you wish to delete.
- In the Node Information area on the Basic Information page, locate the node you wish to delete and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
- The status of the instance in the instance list is Deleting node.
- After the deletion, the instance status becomes Available.
Procedure
- Log in to the GeminiDB console.
- On the Instances page, locate the target instance and click its name.
- In the Node Information area on the Basic Information page, locate the node you wish to delete and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
- The status of the instance in the instance list is Deleting node.
- After the deletion, the instance status becomes Available.
-Precautions
- If you delete a DB instance, all the data in it and all automated backups are automatically deleted as well and cannot be restored, so exercise caution when performing this operation.
- If you delete an instance, all nodes in the instance are also deleted.
diff --git a/docs/geminidb/umn/nosql_03_0007.html b/docs/geminidb/umn/nosql_03_0007.html index 664eac2d..1bdbad0d 100644 --- a/docs/geminidb/umn/nosql_03_0007.html +++ b/docs/geminidb/umn/nosql_03_0007.html @@ -1,7 +1,7 @@Procedure
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, locate the DB instance you wish to delete and choose More > Delete in the Operation column.
- On the displayed page, click Yes.
Deleted DB instances are not displayed in the instance list.
+Procedure
- Log in to the GeminiDB console.
- On the Instances page, locate the instance you want to delete and choose More > Delete in the Operation column.
- On the displayed page, click Yes.
Deleted DB instances are not displayed in the instance list.
Managing Automated Backups
-GeminiDB Cassandra creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure you do not lose your data.
+GeminiDB Cassandra API creates automated backups to ensure data reliability. If a database or table is maliciously or accidentally deleted, backups can help you ensure you do not lose your data.
-Automated Backup Policy
Automated backups are generated according to a backup policy and saved as packages in OBS buckets to ensure data confidentiality and durability. You are advised to regularly back up your database, in case it becomes faulty or damaged. However, backing up data might affect the database read and write performance so it is recommended that you enable automated backups during off-peak hours.
When you create a DB instance, an automated backup policy is enabled by default.- Retention Period: Automated backup files are saved for seven days by default. The backup retention period can range from 1 to 35 days.@@ -11,10 +11,10 @@
- If the retention period is less than seven days, the system automatically backs up data every day.
- The system checks existing automated backup files and deletes the files that exceed the backup retention period you set.
- Time Window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is in GMT format. If the DST or standard time is switched, the backup time segment changes with the time zone.
- After a DB instance is created, you can modify the automated backup policy as needed. You can change the time window after the DB instance is created. The system backs up data based on the automated backup policy you have set.
- If the automated backup policy is disabled, any automated backups in progress stop immediately.
Modifying an Automated Backup Policy
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the DB instance you wish to modify the policy for.
- On the Backups & Restorations page, click Modify Backup Policy. In the displayed dialog box, set the backup policy. Then, click Yes to save the configuration.
For details about how to set a backup policy, see Automated Backup Policy.
+-Modifying an Automated Backup Policy
- Log in to the GeminiDB console.
- On the Instances page, click the DB instance you wish to modify the policy for.
- On the Backups & Restorations page, click Modify Backup Policy. In the displayed dialog box, set the backup policy. Then, click Yes to save the configuration.
For details about how to set a backup policy, see Automated Backup Policy.
- Check or manage the generated backups on the Backup Management page or on the Backups & Restorations page.
Disabling Automated Backup Policy
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the DB instance you wish to modify the policy for.
- On the Backups & Restorations page, click Modify Backup Policy.
- In the displayed dialog box, click
to disable the backup policy and click Yes.When disabling the automated backup policy, you can decide whether to delete the automated backups by selecting Delete automated backups.- If you select it, all backup files within the retention period will be deleted. No automated backups are displayed in the backup list until you enable the automated backup policy again.
- If you do not select it, all backup files within the retention period will be retained, but you can still manually delete them later if needed. For details, see section Deleting an Automated Backup.
diff --git a/docs/geminidb/umn/nosql_03_0012.html b/docs/geminidb/umn/nosql_03_0012.html index d47bb57f..cf4650fc 100644 --- a/docs/geminidb/umn/nosql_03_0012.html +++ b/docs/geminidb/umn/nosql_03_0012.html @@ -2,8 +2,8 @@Disabling Automated Backup Policy
- Log in to the GeminiDB console.
- On the Instances page, click the DB instance you wish to modify the policy for.
- On the Backups & Restorations page, click Modify Backup Policy.
- In the displayed dialog box, click to disable the backup policy and click Yes.When disabling the automated backup policy, you can decide whether to delete the automated backups by selecting Delete automated backups.
- If you select it, all backup files within the retention period will be deleted. No automated backups are displayed in the backup list until you enable the automated backup policy again.
- If you do not select it, all backup files within the retention period will be retained, but you can still manually delete them later if needed. For details, see section Deleting an Automated Backup.
If the automated backup policy is disabled, any automated backups in progress stop immediately.
If the automated backup policy is enabled, the system will delete automated backups as they expire. You cannot delete them manually.
-
The deletion operation is irreversible, so exercise caution when performing this operation.
- Method 1
- On the Instance Management page, click the DB instance you wish to delete backups for.
- On the Backups & Restorations page, locate the backup you wish to delete and click Delete.
- In the Delete Backup dialog box, confirm the backup information and click Yes.
- Method 1
- On the Instances page, click the DB instance you wish to delete backups for.
- On the Backups & Restorations page, locate the backup you wish to delete and click Delete.
- In the Delete Backup dialog box, confirm the backup information and click Yes.
- Method 2
- On the Backup Management page, locate the target backup and click Delete.
- In the Delete Backup dialog box, confirm the backup information and click Yes.
Setting Alarm Rules
Scenarios
You can set alarm rules to customize the monitored objects and notification policies and to stay aware of the database operating status.
-The alarm rules include alarm rule name, instance, metric, threshold, monitoring interval and whether to send notification. This section describes how to set alarm rules.
- For more information about GeminiDB alarm rules, see Cloud Eye User Guide.
+The alarm rules include alarm rule names, monitored objects, metric, thresholds, monitoring intervals, and whether to send notifications. This section describes how to set an alarm rule.
+ For more information about GeminiDB alarm rules, see Cloud Eye User Guide.
Procedure
- Log in to the management console.
- After the alarm rule is set, the system automatically notifies you when an alarm is triggered.
Viewing Metrics
-Scenarios
Cloud Eye monitors GeminiDB running statuses. You can obtain the monitoring metrics of GeminiDB on the management console.
+-Scenarios
Cloud Eye monitors GeminiDB running statuses. You can obtain the metrics of GeminiDB on the management console.
Monitored data requires a period of time for transmission and display. The status of the monitored object displayed on the Cloud Eye page is the status obtained 5 to 10 minutes before. You can view the monitored data of a newly created DB instance 5 to 10 minutes later.
-Prerequisites
Procedure
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the target DB instance.
- In the Node Information area on the Basic Information page, click View Metric in the Operation column.
- In the monitoring area, you can select a duration to view the monitoring data.
You can view the monitoring data of the service in the last 1, 3, or 12 hours.
+diff --git a/docs/geminidb/umn/nosql_03_0014.html b/docs/geminidb/umn/nosql_03_0014.html index 1d65a41a..f71e93e6 100644 --- a/docs/geminidb/umn/nosql_03_0014.html +++ b/docs/geminidb/umn/nosql_03_0014.html @@ -33,14 +33,14 @@Procedure
- Log in to the GeminiDB console.
- On the Instance Management page, click the target DB instance.
- In the Node Information area on the Basic Information page, click View Metric in the Operation column.
- In the monitoring area, you can select a duration to view the monitoring data.
You can view the monitoring data of the service in the last 1, 3, or 12 hours.
To view the monitoring curve in a longer time range, click
to enlarge the graph.
Adding a Tag
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the instance you wish to add tags for to go to the Basic Information page.
- In the navigation pane on the left, click Tags.
- On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value, and click OK.
- View and manage tags on the Tags page.
-Adding a Tag
- Log in to the GeminiDB console.
- On the Instances page, click the name of the target instance to go to the Basic Information page.
- In the navigation pane on the left, click Tags.
- On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value, and click OK.
- View and manage tags on the Tags page.
Editing a Tag
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the instance you wish to add tags for to go to the Basic Information page.
- In the navigation pane on the left, click Tags.
- 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
- Log in to the GeminiDB console.
- On the Instances page, click the name of the target instance to go to the Basic Information page.
- In the navigation pane on the left, click Tags.
- 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.
- View and manage tags on the Tags page.
Deleting a Tag
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the instance you wish to delete tags for to go to the Basic Information page.
- In the navigation pane on the left, click Tags.
- On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
- After a tag has been deleted, it will not be displayed on the Tags page.
-Deleting a Tag
- Log in to the GeminiDB console.
- On the Instances page, click the name of the target instance to go to the Basic Information page.
- In the navigation pane on the left, click Tags.
- On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
- After a tag has been deleted, it will not be displayed on the Tags page.
Searching an Instance by Tag
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click Search by Tag in the upper right corner of the instance list.
- 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
- Log in to the GeminiDB console.
- On the Instances page, click Search by Tag in the upper right corner of the instance list.
- 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_0015.html b/docs/geminidb/umn/nosql_03_0015.html index 3f4694ae..e4006ded 100644 --- a/docs/geminidb/umn/nosql_03_0015.html +++ b/docs/geminidb/umn/nosql_03_0015.html @@ -29,7 +29,7 @@- NUMPROCESSES is the number of exported threads. The range is divided by the number of threads. The more threads are exported, the smaller the ranges are. If the number of threads is too large, the server may be overloaded and the export may fail. You should select a suitable number of threads for export.
The default number of threads is calculated as follows: <Number of vCPUs>-1
- RATEFILE is the rate file. After the file path is specified, the instantaneous rate of the export process is displayed for evaluating the export performance.
- PAGESIZE is the number of rows queried in a single page. The default value is 1000. Do not set this parameter to a small value, or the export performance will suffer.
- BEGINTOKEN and ENDTOKEN are the range to be exported. By default, all data is exported.
- MAXATTEMPTS is the number of retries for each query. If the maximum number of retries of a query is reached, the export fails.
- MAXOUTPUTSIZE is the maximum number of rows in an exported file. If the number of exported rows is greater than the value, another file is generated. By default, the number of rows is not limited.
./cqlsh <DB_HOST> -e "COPY cycling.cyclist_name TO '/home/cas/copydata/cycling.cyclist_name' with MAXOUTPUTSIZE=1"
-- RESULTFILE is the path of the result file. If this parameter is not set, the result file is generated in the current directory by default. If there is already a result file in the directory, the file will be renamed. The exported results show the following information: whether the export is successful, total number of exported rows and rate, number of exported ranges, number of successful or failed ranges, and number of exported rows in each range.
- DATAFORMATS is the data format to be exported. The value can be csv or json. The default value is csv. If the value is in set to json, data will be exported in JSON format.
- WHERECONDITION is the query criteria to be exported. The query criteria can be exported. For non-primary-key columns, the export performance can be improved if the query is based on indexes.
- Supported operators: >=, <=, >, <, and =
- If the value contains special characters, for example, ",><=', add double quotation marks to the value.
- RESULTFILE is the path of the result file. If this parameter is not set, the result file is generated in the current directory by default. If there is already a result file in the directory, the file will be renamed. The exported results show the following information: whether the export is successful, total number of exported rows and rate, number of exported ranges, number of successful or failed ranges, and number of exported rows in each range.
- DATAFORMATS is the data format to be exported. The value can be csv or json. The default value is csv. If the value is in set to json, data will be exported in JSON format.
- WHERECONDITION is the query criteria to be exported. The query criteria can be exported. For non-primary-key columns, the export performance can be improved if the query is based on indexes.
- Supported operators: >=, <=, >, <, and =
- If the value contains special characters, for example, ",><=', add double quotation marks to the value.
COPY FROM
- Command format:
COPY <table name> [(<column>, ...)] FROM <file name> WITH <copy option> [AND <copy option> ...]
diff --git a/docs/geminidb/umn/nosql_03_0016.html b/docs/geminidb/umn/nosql_03_0016.html index 7d013dcb..8ca867ea 100644 --- a/docs/geminidb/umn/nosql_03_0016.html +++ b/docs/geminidb/umn/nosql_03_0016.html @@ -5,10 +5,10 @@
-Precautions
If the instance status is Available, Backing up, Checking restoration, Scaling up or certain nodes become abnormal, you can reset the administrator password.
Method 1
- Log in to the GeminiDB console.
- On the Instance Management page, locate the DB instance you wish to reset the password for and choose More > Reset Password in the Operation column.
- Enter and confirm the new administrator password and click OK.
The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
+-Method 1
- Log in to the GeminiDB console.
- On the Instances page, locate the DB instance you wish to reset the password for and choose More > Reset Password in the Operation column.
- Enter and confirm the new administrator password and click OK.
The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
diff --git a/docs/geminidb/umn/nosql_03_0025.html b/docs/geminidb/umn/nosql_03_0025.html index daa3e3b0..6d9f2a40 100644 --- a/docs/geminidb/umn/nosql_03_0025.html +++ b/docs/geminidb/umn/nosql_03_0025.html @@ -3,13 +3,13 @@Method 2
- Log in to the GeminiDB console.
- On the Instance Management page, click the DB instance you wish to reset the password for. The Basic Information page is displayed.
- In the DB Information area, click Reset Password in the Administrator field.
- Enter and confirm the new administrator password and click OK.
The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
+Method 2
- Log in to the GeminiDB console.
- On the Instances page, click the DB instance you wish to reset the password for. The Basic Information page is displayed.
- In the DB Information area, click Reset Password in the Administrator field.
- Enter and confirm the new administrator password and click OK.
The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
Changing a DB Instance Name
--Scenarios
This section describes how to change a GeminiDB Cassandra instance name to identify different DB instances.
Method 1
- Log in to the GeminiDB console.
- On the Instance Management page, click
to the right of the instance whose name you wish to change.- To submit the change, click OK.
The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
+-Method 1
- Log in to the GeminiDB console.
- On the Instances page, click to the right of the instance whose name you wish to change.
- To submit the change, click OK.
The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- To cancel the change, click Cancel.
- To submit the change, click OK.
- View the results on the Instance Management page.
- View the results on the Instances page.
Method 2
- Log in to the GeminiDB console.
- On the Instance Management page, click the instance whose name you wish to change.
- In the Instance Information area on the Basic Information page, click
in the DB Instance Name field to change the instance name.- To submit the change, click
.The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
+Method 2
- Log in to the GeminiDB console.
- On the Instances page, click the instance whose name you wish to change.
- In the Instance Information area on the Basic Information page, click in the DB Instance Name field to change the instance name.
- To submit the change, click .
The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- To cancel the change, click
.
- To submit the change, click
- View the results on the Instance Management page.
- View the results on the Instances page.
- To submit the change, click
diff --git a/docs/geminidb/umn/nosql_03_0026.html b/docs/geminidb/umn/nosql_03_0026.html index 37a330ff..9eb716e0 100644 --- a/docs/geminidb/umn/nosql_03_0026.html +++ b/docs/geminidb/umn/nosql_03_0026.html @@ -7,12 +7,12 @@
- To submit the change, click OK.
Procedure
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the DB instance you wish to change the CPU and memory for.
- In the in DB Information area on the Basic Information page, click Change next to the Instance Class field.
- On the displayed page, select the desired vCPUs and memory and click Next.
- On the displayed page, confirm the instance class.
- 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 to change the instance class.
- View the DB instance class change result.
Go to the Basic Information page and in the DB Information area you can see the new instance class.
+-Procedure
- Log in to the GeminiDB console.
- On the Instances page, locate the target instance and click its name.
- In the in DB Information area on the Basic Information page, click Change next to the Specifications field.
- On the displayed page, select the desired vCPUs and memory and click Next.
- 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.
- View the DB instance class change result.
Go to the Basic Information page and in the Specifications area you can see the new specifications.
diff --git a/docs/geminidb/umn/nosql_03_0028.html b/docs/geminidb/umn/nosql_03_0028.html index f9e02919..fa12a072 100644 --- a/docs/geminidb/umn/nosql_03_0028.html +++ b/docs/geminidb/umn/nosql_03_0028.html @@ -3,7 +3,7 @@Method 2
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, locate the instance you want to change the class for and choose in the Operation column.
- On the displayed page, select the desired vCPUs and memory and click Next.
- On the displayed page, confirm the instance class.
- 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 to change the instance class.
- View the DB instance class change result.
Go to the Basic Information page and in the DB Information area you can see the new instance class.
+Method 2
- Log in to the GeminiDB console.
- On the Instances page, locate the instance whose specifications you want to change and choose Change Specifications in the Operation column.
- On the displayed page, select the desired vCPUs and memory and click Next.
- 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.
- View the DB instance class change result.
Go to the Basic Information page and in the Specifications area you can see the new specifications.
Slow Query Logs
-Scenarios
GeminiDB allows you to view slow query logs of databases. The unit of the execution time is ms. With slow query logs, you can identify and optimize slowly executed statements.
Viewing Log Details
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, click Slow Query Logs.
- On the Slow Query Logs page, set search criteria and click Search to view log information.
- If you select All nodes, the slow query logs of all nodes in the DB instance are displayed.
- Slow query logs of a node in different time periods
- Slow query statements of the following level
+diff --git a/docs/geminidb/umn/nosql_05_0002.html b/docs/geminidb/umn/nosql_05_0002.html index e31c6fb4..45c8b38e 100644 --- a/docs/geminidb/umn/nosql_05_0002.html +++ b/docs/geminidb/umn/nosql_05_0002.html @@ -3,7 +3,7 @@
Viewing Log Details
- Log in to the GeminiDB console.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, click Slow Query Logs.
- On the Slow Query Logs page, set search criteria and click Search to view log information.
- If you select All nodes, the slow query logs of all nodes in the DB instance are displayed.
- Slow query logs of a node in different time periods
- Slow query statements of the following level
Creating a Parameter Template
You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.
Each user can create up to 100 parameter templates. All types of instances in the same project can share the quota.
-diff --git a/docs/geminidb/umn/nosql_05_0004.html b/docs/geminidb/umn/nosql_05_0004.html index 80e03d0b..f3bf0c35 100644 --- a/docs/geminidb/umn/nosql_05_0004.html +++ b/docs/geminidb/umn/nosql_05_0004.html @@ -3,7 +3,7 @@Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, choose Parameter Template Management.
- On the Parameter Template Management page, click Create Parameter Template.
- Select a compatible DB engine version, name the parameter group, add the parameter group description, and click OK to create a parameter group template.
- Compatible API: Select the API type that is compatible with your DB engine parameter template.
- DB Engine Version: Select a DB engine version, for example, 3.11.
- Parameter Template Name: The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
- Description: The description can contain a maximum of 256 characters except the carriage return character and the following special characters: > ! < " & ' =
Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, choose Parameter Template Management.
- On the Parameter Template Management page, click Create Parameter Template.
- Select a compatible DB engine version, name the parameter group, add the parameter group description, and click OK to create a parameter group template.
- Compatible API: Select the API type that is compatible with your DB engine parameter template.
- DB Engine Version: Select a DB engine version, for example, 3.11.
- Parameter Template Name: The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
- Description: The description can contain a maximum of 256 characters except the carriage return character and the following special characters: > ! < " & ' =
- On the Parameter Template Management page, view the created parameter template.
Exporting a Parameter Template
-Scenarios
- You can export a parameter template of a DB instance for future use. To learn how to apply the exported parameter template to a DB instance, refer to section Applying a Parameter Template.
- You can export the parameter template details (parameter names, values, and descriptions) of a DB instance to a CSV file for review and analysis.
Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, choose Instance Management. On the displayed page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the Parameters tab, above the parameter list, click Export.
- Parameter Template: You can export the parameters of the DB instance to a template for future use.In the displayed dialog box, configure required details and click OK.
- The template name can be up to 64 characters long. It can contain only uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_), and periods (.).
- The template description consists of a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, choose Instance Management. On the displayed page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the Parameters tab, above the parameter list, click Export.
- Parameter Template: You can export the parameters of the DB instance to a template for future use.In the displayed dialog box, configure required details and click OK.
- The template name can be up to 64 characters long. It can contain only uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_), and periods (.).
- The template description consists of a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.
diff --git a/docs/geminidb/umn/nosql_05_0005.html b/docs/geminidb/umn/nosql_05_0005.html index f83e6975..b4e7905e 100644 --- a/docs/geminidb/umn/nosql_05_0005.html +++ b/docs/geminidb/umn/nosql_05_0005.html @@ -3,10 +3,10 @@Comparing Parameter Templates
-Scenarios
This section guides you on how to compare two parameter templates of the same node type and DB engine version to know their current settings.
Comparing Parameter Templates
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- In the parameter template list, locate the parameter template that you created and click Compare in the Operation column.
- In the displayed dialog box, select a parameter template that shares the same DB engine with the template 1 and click OK.
- If their settings are different, the parameter names and values of both parameter templates are displayed.
- If their settings are the same, no data is displayed.
-Comparing Parameter Templates
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- In the parameter template list, locate the parameter template that you created and click Compare in the Operation column.
- In the displayed dialog box, select a parameter template that shares the same DB engine with the template 1 and click OK.
- If their settings are different, the parameter names and values of both parameter templates are displayed.
- If their settings are the same, no data is displayed.
diff --git a/docs/geminidb/umn/nosql_05_0006.html b/docs/geminidb/umn/nosql_05_0006.html index 72373618..f4ce6de0 100644 --- a/docs/geminidb/umn/nosql_05_0006.html +++ b/docs/geminidb/umn/nosql_05_0006.html @@ -4,7 +4,7 @@Comparing Parameter Templates of a Specified Instance
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, choose Instance Management.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the Parameters tab, click Compare above the parameter list.
- In the displayed dialog box, select a parameter template to be compared and click OK.
- If their settings are different, the parameter names and values of both parameter templates are displayed.
- If their settings are the same, no data is displayed.
Comparing Parameter Templates of a Specified Instance
- Log in to the GeminiDB console.
- In the navigation pane on the left, choose Instance Management.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the Parameters tab, click Compare above the parameter list.
- In the displayed dialog box, select a parameter template to be compared and click OK.
- If their settings are different, the parameter names and values of both parameter templates are displayed.
- If their settings are the same, no data is displayed.
-Scenarios
You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template. You can also export the parameter template to generate a new parameter template for future use.
Default parameter templates cannot be replicated, but you can create parameter templates based on the default templates provided.
Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and click Replicate in the Operation column.
Alternatively, click the target DB instance on the Instance Management page. On the Parameters page, click Export to generate a new parameter template for future use.
+Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and click Replicate in the Operation column.
Alternatively, click the target DB instance on the Instance Management page. On the Parameters page, click Export to generate a new parameter template for future use.
- In the displayed dialog box, enter the parameter template name and description and click OK.
- The template name can be up to 64 characters long. It can contain only uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_), and periods (.).
- The description contains a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.
Resetting a Parameter Template
-Scenarios
You can reset all parameters in a custom parameter template to their default settings.
Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and choose More > Reset in the Operation column.
- Click Yes to reset the parameter template.
Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and choose More > Reset in the Operation column.
- Click Yes to reset the parameter template.
diff --git a/docs/geminidb/umn/nosql_05_0008.html b/docs/geminidb/umn/nosql_05_0008.html index 5352ecb4..f50445e6 100644 --- a/docs/geminidb/umn/nosql_05_0008.html +++ b/docs/geminidb/umn/nosql_05_0008.html @@ -3,7 +3,7 @@Applying a Parameter Template
-Scenarios
Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances.
Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, apply a default template or a custom template to a target DB instance:
- To apply a default template, click Default Templates, locate the target parameter template, and in the Operation column, click Apply.
- To apply a custom template, click Custom Templates, locate the target parameter template, and in the Operation column, choose More > Apply.
Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Templates page, perform the following operations based on the template type:
- To apply a default template, click Default Templates, locate the target parameter template, and in the Operation column, click Apply.
- To apply a custom template, click Custom Templates, locate the target parameter template, and in the Operation column, choose More > Apply.
A parameter template can be applied to one or more DB instances.
- In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.
After a parameter template is applied, you can view its application records.
Viewing Application Records of a Parameter Template
-Scenarios
You can view the application records of a parameter template.
diff --git a/docs/geminidb/umn/nosql_05_0010.html b/docs/geminidb/umn/nosql_05_0010.html index 111230f1..9abc9951 100644 --- a/docs/geminidb/umn/nosql_05_0010.html +++ b/docs/geminidb/umn/nosql_05_0010.html @@ -3,7 +3,7 @@Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, locate the target parameter template and choose More > View Application Record in the Operation column.
You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and the causes of any failures that have occurred.
+Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, locate the target parameter template and choose More > View Application Record in the Operation column.
You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and the causes of any failures that have occurred.
Modifying a Parameter Template Description
--Scenarios
You can modify the description of a custom parameter template if needed.
diff --git a/docs/geminidb/umn/nosql_05_0011.html b/docs/geminidb/umn/nosql_05_0011.html index fc1e4db7..17221384 100644 --- a/docs/geminidb/umn/nosql_05_0011.html +++ b/docs/geminidb/umn/nosql_05_0011.html @@ -5,7 +5,7 @@Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and click
in the Description column. - Enter a new description. You can click
to submit or 
to cancel the modification.- After you submit the modification, you can view the new description in the Description column on the Parameter Template Management page.
- The description can include up to 256 characters but cannot contain the following special characters: >!<"&'=
Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click the Custom Templates tab. Locate the target parameter template and click in the Description column.
- Enter a new description. You can click to submit or to cancel the modification.
- After you submit the modification, you can view the new description in the Description column on the Parameter Template Management page.
- The description can include up to 256 characters but cannot contain the following special characters: >!<"&'=
- Deleted templates cannot be recovered, so exercise caution when performing this operation.
- Default parameter templates cannot be deleted.
Procedure
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Template Management page, click Custom Templates. Locate the parameter template you wish to delete and choose More > Delete in the Operation column.
- Click Yes to delete the parameter template.
Procedure
- Log in to the GeminiDB console.
- In the navigation pane on the left, click Parameter Template Management.
- On the Parameter Templates page, click Custom Templates. Locate the parameter template you want to delete and choose More > Delete in the Operation column.
- Click Yes to delete the parameter template.
diff --git a/docs/geminidb/umn/nosql_05_0012.html b/docs/geminidb/umn/nosql_05_0012.html index 4c4b5ac5..6c90c5df 100644 --- a/docs/geminidb/umn/nosql_05_0012.html +++ b/docs/geminidb/umn/nosql_05_0012.html @@ -5,10 +5,10 @@- In a newly exported or created parameter template, change history is left blank.
Viewing Change History of a Custom Parameter Template
- Log in to the GaussDB NoSQL console.
- In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates page, click the parameter template you wish to view.
- In the navigation pane on the left, choose Change History. Then, view the parameter name, original parameter value, new parameter value, modification status, and modification time.
You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.
+-Viewing Change History of a Custom Parameter Template
- Log in to the GeminiDB console.
- In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates page, click the parameter template you wish to view.
- In the navigation pane on the left, choose Change History. Then, view the parameter name, original parameter value, new parameter value, modification status, and modification time.
You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.
Viewing Change History of DB Instance Parameters
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, click Parameters. On the Change History tab, view the parameter name, original parameter value, new parameter value, modification status, and modification time.
Viewing Change History of DB Instance Parameters
- Log in to the GeminiDB console.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, click Parameters. On the Change History tab, view the parameter name, original parameter value, new parameter value, modification status, and modification time.
diff --git a/docs/geminidb/umn/nosql_06_0003.html b/docs/geminidb/umn/nosql_06_0003.html new file mode 100644 index 00000000..2ba80d5e --- /dev/null +++ b/docs/geminidb/umn/nosql_06_0003.html @@ -0,0 +1,177 @@ + + +Creating a GeminiDB Cassandra Instance
++This section describes how to create a DB instance that is compatible with Cassandra APIs.
++Procedure
- Log in to the GeminiDB console by following Logging In to the GeminiDB Console.
- On the Instances page, click Create DB Instance.
- On the displayed page, select your DB instance specifications and click Create Now.
+
+ +
+Table 1 Basic information Parameter
+Description
+Region
+The region where the tenant is located.
+NOTICE:+Select the region nearest where you will be accessing the DB from so latency can be kept to a minimum and response time will be faster. Also, products deployed in different regions cannot communicate with each other through a private network and you cannot change the region of an instance after creating the instance.
+DB Instance Name
+The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
+After the DB instance is created, you can change the DB instance name. For details, see section Changing a DB Instance Name.
+Compatible API
+Cassandra
+DB Instance Type
+Cluster
+DB Engine Version
+3.11
+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 connection.
++ +
+Table 2 Specifications and storage Parameter
+Description
+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.
+Nodes
+The number of nodes ranges from 3 to 200. Select the number of nodes based on the site requirements.
+After a DB instance is created, you can add nodes. For details, see Adding Nodes.
+Storage Space
+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.
+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.
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.
+ +
+Table 3 Network Parameter
+Description
+VPC
+The virtual network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC.
+If no VPC is available, the system creates one for you.
+For details on how to create a subnet, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.
+NOTE:+After the GeminiDB Cassandra instance is created, the VPC where the instance resides cannot be changed.
+Subnet
+A subnet provides dedicated network resources that are logically isolated from other networks for network security.
+Security Group
+A security group controls access between GeminiDB instances and other services. When you select a security group, you must ensure that it allows the client to access DB instances.
+If no security group is available, the system creates one for you.
++ +
+Table 4 Database configuration Parameter
+Description
+Administrator
+The default administrator account is rwuser.
+Administrator Password
+Set a password for the administrator. The password:
+- Must be 8 to 32 characters long.
- Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?
- For security reasons, you must select a strong password. The system will verify the password strength.
Keep this password secure. If you lose it, the system cannot retrieve it.
+Confirm Password
+Enter the administrator password again.
+Parameter Template
+A parameter template contains engine configuration values that can be applied to one or more instances.
+After a DB instance is created, you can modify parameters to better meet your service requirements. For details, see Modifying a Parameter Template.
++
+Table 5 Tags Parameter
+Description
+Tags
+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 (-).
+ - 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.
+ - On the displayed page, confirm the DB instance details.
- If you need to modify the specifications, click Previous to return to the previous page.
- If you do not need to modify the specifications, click Submit to start creating the instance.
- On the Instances page, view and manage your DB instances.
- Creating a DB instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
- After the creation is complete, the status changes to Available.
You can click
+ in the upper right corner of the page to refresh the DB instance statuses. - During creation, an automated backup policy is enabled by default. A full backup is automatically triggered after a DB instance is created.
++ diff --git a/docs/geminidb/umn/nosql_increase_nodes.html b/docs/geminidb/umn/nosql_increase_nodes.html index 260ad2d0..cc38a799 100644 --- a/docs/geminidb/umn/nosql_increase_nodes.html +++ b/docs/geminidb/umn/nosql_increase_nodes.html @@ -5,7 +5,7 @@++Parent topic: Getting Started with GeminiDB Cassandra+-Precautions
- Adding nodes may lead to the decrease of operations per second (OPS). You are advised to perform this operation during off-peak hours.
- You can only add nodes when the instance status is Available or Checking restoration.
- A DB instance cannot be deleted when one or more nodes are being added.
Procedure
- Log in to the GaussDB NoSQL console.
- On the Instance Management page, click the DB instance you wish to add nodes for.
- In the Node Information area on the Basic Information page, click Add Node.
- Specify Add Nodes and click Next.
- By default, the specifications of new nodes are the same as the DB instance and cannot be modified.
- Up to 200 nodes can be added to a GeminiDB Cassandra instance.
Procedure
- Log in to the GeminiDB console.
- On the Instances page, locate the target instance and click its name.
- In the Node Information area on the Basic Information page, click Add Node.
- Specify Add Nodes and click Next.
- By default, the specifications of new nodes are the same as the DB instance and cannot be modified.
- Up to 200 nodes can be added to a GeminiDB Cassandra instance.
- On the displayed page, confirm the node configuration details.
- 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 to add the nodes.
- View the result of adding nodes.
- The status of the DB instance in the instance list is Adding node.
- After the nodes are added, the DB instance status becomes Available.
- Click the DB instance name. In the Node Information area on the Basic Information page, view the information about the new nodes.
-Precautions
Storage space can only be scaled up. It cannot be scaled down.
Procedure
- Log in to the GeminiDB console.
- On the Instance Management page, click the DB instance you wish to scale up.
- In the Storage Space area on the Basic Information page, click Scale.
- On the displayed page, specify the new storage capacity and click Next.
Select at least 1 GB each time you scale up the storage, and the storage size must be an integer.
+Procedure
- Log in to the GeminiDB console.
- On the Instances page, click the target instance name.
- In the Storage Space area on the Basic Information page, click Scale.
- On the displayed page, specify the new storage capacity and click Next.
Select at least 1 GB each time you scale up the storage, and the storage size must be an integer.
- On the displayed page, confirm the storage space.
- 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 to scale up the storage space.
- Check the scale-up result.
- The status of the DB instance in the instance list is Scaling up.
- After the scale up is completed, the DB instance status becomes Available.
- In the Storage Space area on the Basic Information page, check whether the scale up was successful.
Configuring Auto Scale
++You can enable autoscaling for GeminiDB Cassandra instances. When storage usage reaches the limit, autoscaling is triggered.
+You can enable autoscaling:
+-
+
For details, see Creating a GeminiDB Cassandra Instance.
+ - After creating an instance
For details, see operations in this section.
++ - If you enable autoscaling as a domain user, no additional configuration is required.
- If you enable autoscaling as an IAM user first time, you need to temporarily assign the permission of creating an agency to the user.
+Permission Configuration
If you are using an IAM user, configure the following permissions before enabling autoscaling:+- GeminiDB FullAccess
- IAM fine-grained permission
For details, see Creating a Custom Policy.
+Custom policy in JSON format:
+{ + "Version":"1.1", + "Statement":[ + { + "Effect":"Allow", + "Action":[ + "iam:permissions:listRolesForAgencyOnProject", + "iam:permissions:grantRoleToGroupOnProject", + "iam:agencies:createAgency", + "iam:agencies:listAgencies", + "iam:roles:listRoles", + "iam:roles:createRole" + ] + } + ] +}+ - Creating a User Group and Assigning Permissions
You can create a user group on the IAM console and assign it custom permissions created in 2 and system role Security Administrator.
+ - Adding Users to or Removing Users from a User Group
Log in to the IAM console as a domain or an IAM user. Locate the IAM user that the target instance belongs to and add it to the user group created in 3. The IAM user will inherit permissions of the user group.
+
+Precautions
- 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
- Log in to the GeminiDB console by following Logging In to the GeminiDB Console.
- On the Instances page, click the instance. The Basic Information page is displayed.
- In the Storage Space area, click Auto Scale.Figure 1 Auto Scale+
- Toggle on Auto Scale and specify the parameters below.Figure 2 Configuring autoscaling+ +
+
+Table 1 Parameter description Parameter
+Description
+Auto Scale
+If you toggle on this switch, autoscaling is enabled.
+Trigger If Available Storage Drops To
+When the available storage usage drops to this value or the available storage space drops to 10 GB, autoscaling is triggered.
+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.
+Storage Limit
+Limit of storage (GB) that can be automatically scaled 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.
+ - Click OK.
+ +Automatically Scaling Up Storage of Multiple Instances In Batches
- Log in to the GeminiDB console by following Logging In to the GeminiDB Console.
- Select instances and click Auto Scale.Figure 3 Auto Scale+
- Select an instance, toggle on Auto Scale, and specify the parameters below.Figure 4 Batch Auto Scale+ +
+
+Table 2 Parameter description Parameter
+Description
+Auto Scale
+If you toggle on this switch, autoscaling is enabled.
+Trigger If Available Storage Drops To
+When the available storage usage drops to this value or the available storage space drops to 10 GB, autoscaling is triggered.
+Increase By
+Percentage of the current storage to be automatically scaled. The value can be 10, 15, or 20. At least 100 GB is added each time.
+Storage Limit
+This parameter cannot be customized. By default, the storage is scaled up the maximum of the selected instance.
+ - Click OK.
++++Parent topic: DB Instance Management+
- Parameter Template: You can export the parameters of the DB instance to a template for future use.
- Parameter Template: You can export the parameters of the DB instance to a template for future use.
- Creating a GeminiDB Cassandra Instance