2023-10-25
Modified the following content:
Added specifications (2 vCPUs | 8 GB) in DB Instance Specifications.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0004.html b/docs/gaussdb_mysql/umn/gaussdb_02_0004.html index 535f86402..be7131d1b 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0004.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0004.html @@ -3,7 +3,7 @@Step 1: Create a DB Instance
Scenarios
This section describes how to create a DB instance on the management console.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select a region and a project. - Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click Create DB Instance.
- On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click Create DB Instance.
- On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.-
Table 1 Basic information Parameter
Description
@@ -12,7 +12,7 @@Region
A region where the tenant is located. You can change it on the creation page, or go back to the Instance Management page and change it in the upper left corner.
+A region where the tenant is located. You can change it on the creation page, or go back to the Instances page and change it in the upper left corner.
NOTICE:Products in different regions cannot communicate with each other over a private network and you cannot change the region of a DB instance after creating the instance.
Table 2 Specifications and storage Parameter
+-Table 2 Specifications and storage Parameter
Description
+Description
Table 3 Network Parameter
+-Table 3 Network Parameter
Description
+Description
Table 4 Database configuration Parameter
+-Table 4 Database configuration Parameter
Description
Table 5 Parameter template Parameter
+Table 5 Parameter template Parameter
Description
+Description
- Confirm your specifications.
- If you need to modify your settings, click Previous.
- If you do not need to modify your settings, click Submit.
- To view and manage DB instances, go to the Instance Management page.
- During the creation process, the DB instance status is Creating. When the status of the created instance is Available, the DB instance can be used.
- An automated backup policy is enabled by default. After the DB instance is created, you can modify this policy as required. An automated full backup is immediately triggered after a DB instance is created.
- The default database port is 3306. After a DB instance is created, you can change its port.
For details, see Changing a Database Port.
+ - To view and manage DB instances, go to the Instances page.
- During the creation process, the DB instance status is Creating. When the status of the created instance is Available, the DB instance can be used.
- An automated backup policy is enabled by default. After the DB instance is created, you can modify this policy as required. An automated full backup is immediately triggered after a DB instance is created.
- The default database port is 3306. After a DB instance is created, you can change its port.
For details, see Changing a Database Port.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html
index a82057e74..52bd6ab79 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html
@@ -12,7 +12,7 @@
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- Configure security group rules.
In the Network Information area on the Basic Information page, click the security group.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- Configure security group rules.
In the Network Information area on the Basic Information page, click the security group.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters and click OK.You can click + to add more inbound rules.
Table 1 Inbound rule parameter description Parameter
Step 1: Create a DB Instance
-Scenarios
This section describes how to create a DB instance on the management console.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click Create DB Instance.
- On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click Create DB Instance.
- On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.-
Table 1 Basic information Parameter
Description
@@ -12,7 +12,7 @@Region
A region where the tenant is located. You can change it on the creation page, or go back to the Instance Management page and change it in the upper left corner.
+A region where the tenant is located. You can change it on the creation page, or go back to the Instances page and change it in the upper left corner.
NOTICE:Products in different regions cannot communicate with each other over a private network and you cannot change the region of a DB instance after creating the instance.
Table 2 Specifications and storage Parameter
+-Table 2 Specifications and storage Parameter
Description
+Description
Table 3 Network Parameter
+-Table 3 Network Parameter
Description
+Description
Table 4 Database configuration Parameter
+-Table 4 Database configuration Parameter
Description
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0018.html b/docs/gaussdb_mysql/umn/gaussdb_03_0018.html index 7b0c5a220..29e4274c9 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0018.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0018.html @@ -2,7 +2,7 @@Table 5 Parameter template Parameter
+Table 5 Parameter template Parameter
Description
+Description
- Confirm your specifications.
- If you need to modify your settings, click Previous.
- If you do not need to modify your settings, click Submit.
- To view and manage DB instances, go to the Instance Management page.
- During the creation process, the DB instance status is Creating. When the status of the created instance is Available, the DB instance can be used.
- An automated backup policy is enabled by default. After the DB instance is created, you can modify this policy as required. An automated full backup is immediately triggered after a DB instance is created.
- The default database port is 3306. After a DB instance is created, you can change its port.
For details, see Changing a Database Port.
+ - To view and manage DB instances, go to the Instances page.
- During the creation process, the DB instance status is Creating. When the status of the created instance is Available, the DB instance can be used.
- An automated backup policy is enabled by default. After the DB instance is created, you can modify this policy as required. An automated full backup is immediately triggered after a DB instance is created.
- The default database port is 3306. After a DB instance is created, you can change its port.
For details, see Changing a Database Port.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html
index 870b2fcfa..5195ea9bd 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html
@@ -5,7 +5,7 @@
- Public accessibility reduces the security of DB instances. Therefore, exercise caution when enabling this function. To achieve a higher transmission rate and security level, you are advised to migrate your applications to the ECS that is in the same region as the GaussDB(for MySQL) DB instance.
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- In the Network Information area, click Bind in the Private IP Address field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance. For details, see Step 3: Configure Security Group Rules.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- In the Network Information area, click Bind in the Private IP Address field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance. For details, see Step 3: Configure Security Group Rules.
- On the EIPs page, view the EIP that has been bound to the DB instance.
-Prerequisites
- You have assigned an EIP on the VPC console.
- If a DB instance has already been bound with an EIP, you must unbind the EIP from the DB instance first before binding a new EIP to it.
Binding an EIP
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click Bind in the Public IP Address (EIP) field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance.
+Binding an EIP
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click Bind in the Public IP Address (EIP) field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance.
- On the EIPs page, view the EIP that has been bound to the DB instance.
To unbind the EIP from the DB instance, see Unbinding an EIP.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html index 8d3fb0d0b..58f8330bc 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html @@ -5,7 +5,7 @@
-Constraints
The port number of the proxy instance is independent of that of the instance. Changing the port number of the DB instance does not change the port number of the proxy 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 Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click
in the Database Port field.The GaussDB(for MySQL) database port ranges from 1025 to 65534, excluding 5342, 5343, 5344, 5345, 12017, 20000, 20201, and 20202, which are occupied by the system and cannot be used.- To submit the change, click
.- In the dialog box, click Yes.
- If you change the database port of a DB instance, the ports of the primary node and read replicas are also changed accordingly and all of them are rebooted.
- This process takes about 1–5 minutes.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click in the Database Port field.The GaussDB(for MySQL) database port ranges from 1025 to 65534, excluding 5342, 5343, 5344, 5345, 12017, 20000, 20201, and 20202, which are occupied by the system and cannot be used.diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0014.html b/docs/gaussdb_mysql/umn/gaussdb_03_0014.html index 859bd7f54..23b613869 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0014.html @@ -172,6 +172,13 @@
- To submit the change, click .
- In the dialog box, click Yes.
- If you change the database port of a DB instance, the ports of the primary node and read replicas are also changed accordingly and all of them are rebooted.
- This process takes about 1–5 minutes.
- In the dialog box, click Yes.
- To cancel the change, click
.
applyParameterGroup
- To submit the change, click
- In the dialog box, click Yes.
- To submit the change, click
-Precautions
Procedure
Deleting a task from the task center
+job
+deleteTaskCenterJob
+Viewing Error Logs
GaussDB(for MySQL) log management allows you to view database-level logs, including error logs and slow SQL query logs.
--Viewing Log Details
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Logs.
- On the Error Logs page, select a node and view the error log details of the node, including:
- Error logs in different time periods
- Error logs of the following levels:
- ALL
- INFO
- WARNING
- ERROR
- FATAL
- NOTE
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html index a98bf961c..1b0145fb0 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html @@ -5,7 +5,7 @@Viewing Log Details
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Logs.
- On the Error Logs page, select a node and view the error log details of the node, including:
- Error logs in different time periods
- Error logs of the following levels:
- ALL
- INFO
- WARNING
- ERROR
- FATAL
- NOTE
GaussDB(for MySQL) supports the following statement types:- SELECT
- INSERT
- UPDATE
- DELETE
- CREATE
- ALTER
- DROP
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html index 67715151a..252caf406 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html @@ -1,10 +1,9 @@Viewing Log Details
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Logs.
- On the Slow Query Logs page, view the slow query log details.
You can view the slow query log records of a specified execution statement type or a specific time period.
+Viewing Log Details
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Logs.
- On the Slow Query Logs page, view the slow query log details.
You can view the slow query log records of a specified execution statement type or a specific time period.
Changing a DB Instance Name
-Scenarios
You can change the name of a GaussDB(for MySQL) DB instance.
+-Scenarios
You can change the name of a GaussDB(for MySQL) DB instance.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0040.html b/docs/gaussdb_mysql/umn/gaussdb_03_0040.html index 28b131fdd..b7d84f5eb 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0040.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0040.html @@ -6,7 +6,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the target DB instance and click
next to it to edit the DB instance name. Then, click OK.The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.
-- To submit the change, click OK.
- To cancel the change, click Cancel.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the instance name and click in the Name/ID column to edit the instance name.
- The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.
- When changing the instance name, you can determine whether to select Change node names synchronously as required. If this option is selected, the names of the corresponding nodes are changed when the instance name is changed. If this option is not selected, only the instance name is changed, and the corresponding node names are not changed.
- If you want to submit the change, click OK. If you want to cancel the change, click Cancel.
- View the result of the change on the Basic Information page.
- - Your database may be unavailable if, for example, data is being backed up or there are modifications being made.
- Rebooting a DB instance will cause service interruption. During this period, the DB instance status is Rebooting.
- DB instances are not available when being rebooted. After the reboot completes, the cached memory will be automatically cleared. The DB instance needs to be warmed up to prevent congestion during peak hours.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the target DB instance and choose in the Operation column.
Alternatively, click the target DB instance. On the displayed page, click Reboot in the upper right corner of the page.
+diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0045.html b/docs/gaussdb_mysql/umn/gaussdb_03_0045.html index 235c222bc..d6ce4a8d6 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0045.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0045.html @@ -3,9 +3,9 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the target DB instance and choose in the Operation column.
Alternatively, click the target DB instance. On the displayed page, click Reboot in the upper right corner of the page.
The read replicas are also rebooted.
- In the displayed Reboot DB Instance dialog box, click Yes.
- Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
Exporting DB Instance Information
-Scenarios
You can export a DB instance list (containing all or selected DB instances) to view and analyze DB instance information.
Exporting Information About All DB Instances
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click
in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export. - After the export task is complete, a .csv file is generated locally.
-Exporting Information About All DB Instances
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
- After the export task is complete, a .csv file is generated locally.
Exporting Information About Selected DB Instances
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, select the DB instances to be exported and click
in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export. - After the export task is complete, a .csv file is generated locally.
Exporting Information About Selected DB Instances
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, select the DB instances to be exported and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
- After the export task is complete, a .csv file is generated locally.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0047.html b/docs/gaussdb_mysql/umn/gaussdb_03_0047.html index 3d0091420..cc0bcd54c 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0047.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0047.html @@ -1,13 +1,13 @@Deleting a DB Instance
-Scenarios
You can manually delete a DB instance on the Instance Management page.
+Scenarios
You can manually delete a DB instance on the Instances page.
- If you delete a DB instance, the read replicas associated with it are also deleted.
- Deleted DB instances cannot be recovered. Exercise caution when performing this operation.
-Constraints
- DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are completed.
- If you delete a DB instance, its automated backups are also deleted and you are no longer charged for them. Manual backups are still retained and will incur additional costs.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the DB instance to be deleted and click More > Delete in the Operation column.
- In the displayed dialog box, click Yes. Refresh the Instance Management page later to check that the deletion is successful.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the DB instance to be deleted and click More > Delete in the Operation column.
- In the displayed dialog box, click Yes. Refresh the Instances page later to check that the deletion is successful.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html index d303b86ec..bc22b1206 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html @@ -8,15 +8,15 @@- The database port is being changed.
- The instance status is Creating, Restoring, Rebooting, Changing port, Changing instance class, Promoting to primary, or Abnormal.
-Precautions
- If you change the administrator password of a DB instance, the passwords of the read replicas associated with the DB instance are also changed accordingly.
- The length of time it takes for the new password to take effect depends on the amount of service data currently being processed by the primary node.
- To prevent brute force cracking and ensure system security, change your password periodically, such as every three or six months.
Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the target DB instance and choose in the Operation column.
- Enter a new password and confirm the password.
Keep this password secure. The system cannot retrieve it.
+-Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the target DB instance and choose in the Operation column.
- Enter a new password and confirm the password.
Keep this password secure. The system cannot retrieve it.
The new password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.
- To submit the new password, click OK.
- To cancel the reset, click Cancel.
Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the DB Instance Information area, click Reset Password in the Administrator field. In the displayed dialog box, enter a new password and confirm the password.
Keep this password secure. The system cannot retrieve it.
+Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the DB Instance Information area, click Reset Password in the Administrator field. In the displayed dialog box, enter a new password and confirm the password.-
Keep this password secure. The system cannot retrieve it.
The new password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html index ab358d030..061d77be0 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html @@ -4,11 +4,11 @@- To submit the new password, click OK.
- To cancel the reset, click Cancel.
The new password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.- To submit the new password, click OK.
- To cancel the reset, click Cancel.
-Scenarios
GaussDB(for MySQL) allows you to create manual backups for available primary nodes. You can restore data from backups to ensure data reliability.
- When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.
Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the target DB instance and choose in the Operation column.
- In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backup Management page.
-Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the target DB instance and choose in the Operation column.
- In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backups page.
Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- On the Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and a description, and click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backup Management page.
Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- On the Backups page, click Create Backup. In the displayed dialog box, enter a backup name and a description, and click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backups page.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0063.html b/docs/gaussdb_mysql/umn/gaussdb_03_0063.html index 17f45e407..4123d1cf1 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0063.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0063.html @@ -3,7 +3,7 @@Restoring Data from a Backup
-Scenarios
You can use an automated or manual backup to restore data to the status when the backup was created. The restoration is at the DB instance level.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Backup Management page, select the backup to be restored and click Restore in the Operation column.
- Click OK. Currently, you can only restore data to a new DB instance.
The Create New Instance page is displayed.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Backups page, select the backup to be restored and click Restore in the Operation column.
- Click OK. Currently, you can only restore data to a new DB instance.
The Create New Instance page is displayed.
- The region, DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
- The database port is 3306 by default.
- Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
- View the restoration results.
A new DB instance is created using the backup data. The instance status changes from Creating to Available.
The new DB instance is independent from the original one. If you want to offload read pressure on the primary node, create one or more read replicas for the new DB instance.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0068.html b/docs/gaussdb_mysql/umn/gaussdb_03_0068.html index 5ac7f13f0..3ff377b3f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0068.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0068.html @@ -5,7 +5,7 @@
- Deleted manual backups cannot be recovered. Exercise caution when performing this operation.
-Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- In the navigation pane on the left, choose Backup Management. On the displayed page, locate the manual backup to be deleted and click Delete in the Operation column.
The following backups cannot be deleted:
+diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0072.html b/docs/gaussdb_mysql/umn/gaussdb_03_0072.html index 823dd6f18..b01f93da3 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0072.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0072.html @@ -8,7 +8,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- In the navigation pane on the left, choose Backups. On the displayed page, locate the manual backup to be deleted and click Delete in the Operation column.
The following backups cannot be deleted:
- Automated backups
- Backups that are being restored
- Click Yes.
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 following the instructions provided in Replicating a Parameter Template.
The following are the key points you should know when using parameters:
- When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances to which the parameter template applies.
- Improper parameter settings may have unintended adverse effects, including degraded performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html index 077620506..e150f6c00 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html @@ -12,7 +12,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, click Create Parameter Template.
- In the displayed dialog box, configure required information and click OK.
- Select a DB engine for the parameter template.
- The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
- The description consists of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: >!<"&'=
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, click Create Parameter Template.
- In the displayed dialog box, configure required information and click OK.
- Select a DB engine for the parameter template.
- The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
- The description consists of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: >!<"&'=
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.
You can use either of the following methods to view monitoring metrics:
+-Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.
You can use either of the following methods to view monitoring metrics:
- Click the target DB instance. On the displayed Basic Information page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.
- At the bottom part of the Basic Information page, locate the target read replica and click View Metric in the Operation column to go to the Cloud Eye console.
- On the Cloud Eye console, view DB instance monitoring metrics.
Cloud Eye can monitor performance metrics from the last 1 hour, last 3 hours, last 12 hours, last 24 hours or last 7 days.
- Changing the CPU and memory specifications will cause the instance to reboot. To prevent service interruptions, change the instance specifications during off-peak hours.
- To prevent traffic congestion during peak hours, you are advised to reboot the DB instance during off-peak hours.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- You can change the instance specifications in either of the following ways:
- On the Instance Management page, locate the target DB instance and choose More > Change Instance Specifications in the Operation column.
- Click the target DB instance to go to the Basic Information page. In the DB Instance Information area, click Change in the Instance Specifications field.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- You can change the instance specifications in either of the following ways:
- On the Instances page, locate the target DB instance and choose More > Change Instance Specifications in the Operation column.
- Click the target DB instance to go to the Basic Information page. In the DB Instance Information area, click Change in the Instance Specifications field.
- On the displayed page, specify the new instance specifications, and click Next.
- On the displayed page, confirm the instance 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 specification change result.
Changing the instance specifications takes 5–15 minutes. During this period, the status of the instance on the Instance Management page is Changing instance specifications. After a few minutes, you can click the instance name to view the new instance specifications on the displayed Basic Information page.
+ - View the DB instance specification change result.
Changing the instance specifications takes 5–15 minutes. During this period, the status of the instance on the Instances page is Changing instance specifications. After a few minutes, you can click the instance name to view the new instance specifications on the displayed Basic Information page.
After the specifications of DB instances 8.0 are changed, the system will change the values of the following parameters accordingly: innodb_buffer_pool_size, innodb_log_buffer_size, max_connections, innodb_buffer_pool_instances, innodb_page_cleaners, innodb_parallel_read_threads, innodb_read_io_threads, innodb_write_io_threads, threadpool_size and query_cache_size.
After a DB instance is created, you can create read replicas for it.
- If you select the single AZ type, read replicas are deployed in the same AZ as the primary node.
- If you select the multi-AZ type, read replicas are deployed in different AZs from the primary node to ensure high reliability.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0113.html b/docs/gaussdb_mysql/umn/gaussdb_03_0113.html index 2adbc88f5..acf5854a2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0113.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0113.html @@ -2,7 +2,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, locate the target DB instance and choose More > Create Read Replica in the Operation column.
Alternatively, click the target DB instance. In the DB Instance Topology area on the Basic Information page, click
+
to create read replicas.Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, locate the target DB instance and choose More > Create Read Replica in the Operation column.
Alternatively, click the target DB instance. In the DB Instance Topology area on the Basic Information page, click
to create read replicas. - On the displayed page, specify Failover Priority and Quantity and then click Create Now.
- After read replicas are created, you can manage them following the instructions provided in Managing a Read Replica.
Promoting a Read Replica to the Primary Node
A GaussDB(for MySQL) DB instance consists of a primary node and multiple read replicas. In addition to automatic failover scenarios, you can perform a manual switchover to promote a read replica to the new primary node.
-Manual Switchover
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- At the bottom of the Basic Information page, locate the read replica to be promoted and click Promote to Primary in the Operation column.
- In the displayed dialog box, click Yes.
- During the manual switchover, an intermittent disconnection may occur for about 30 seconds. Ensure that your applications support automatic reconnection.
- During the manual switchover, the instance status is Promoting to primary and this process takes several seconds or minutes.
- After the switchover is complete, the node running status changes to Available. The node types of the original primary node and read replica have been exchanged.
Services may be intermittently interrupted for several seconds or minutes when the read replica is promoted to the primary node.
+Manual Switchover
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- At the bottom of the Basic Information page, locate the read replica to be promoted and click Promote to Primary in the Operation column.
- In the displayed dialog box, click Yes.
- During the manual switchover, an intermittent disconnection may occur for about 30 seconds. Ensure that your applications support automatic reconnection.
- During the manual switchover, the instance status is Promoting to primary and this process takes several seconds or minutes.
- After the switchover is complete, the node running status changes to Available. The node types of the original primary node and read replica have been exchanged.
Services may be intermittently interrupted for several seconds or minutes when the read replica is promoted to the primary node.
Deleting a Read Replica
-Scenarios
You can manually delete read replicas on the Instance Management page.
+Scenarios
You can manually delete read replicas on the Instances page.
Deleted read replicas cannot be restored. Exercise caution when performing this operation.
-Constraints
- You can delete read replicas only when the DB instance has two or more than two read replicas. A GaussDB(for MySQL) DB instance must have at least one read replica.
- DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are completed.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- At the bottom of the Basic Information page, locate the read replicas to be deleted and choose More > Delete in the Operation column.
For high availability reasons, the system reserves an available read replica. The read replica cannot be deleted until the associated DB instance is deleted.
- - In the displayed dialog box, click Yes. Refresh the Instance Management page later to check that the deletion is successful.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- At the bottom of the Basic Information page, locate the read replicas to be deleted and choose More > Delete in the Operation column.
For high availability reasons, the system reserves an available read replica. The read replica cannot be deleted until the associated DB instance is deleted.
+ - In the displayed dialog box, click Yes. Refresh the Instances page later to check that the deletion is successful.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0018.html b/docs/gaussdb_mysql/umn/gaussdb_05_0018.html index 16cde2516..217d26a6d 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_05_0018.html +++ b/docs/gaussdb_mysql/umn/gaussdb_05_0018.html @@ -4,7 +4,7 @@-Scenarios
Modifications to parameters in a custom parameter template take effect only after you apply this parameter template to target DB instances.
- The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications have different value ranges. If this parameter value is out of range of the DB instance to which the parameter template applies, the maximum value within the range is used.
- A parameter template can be applied only to DB instances of the same DB engine version.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, you can 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 management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, you can 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.
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 apply and click OK.
After the parameter template applies to DB instances successfully, you can view the application records by referring to Viewing Application Records of a Parameter Template.
Viewing Application Records of a Parameter Template
--Scenarios
You can view the application records of a parameter template.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0099.html b/docs/gaussdb_mysql/umn/gaussdb_05_0099.html index 1b3751cb1..5d6525563 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_05_0099.html +++ b/docs/gaussdb_mysql/umn/gaussdb_05_0099.html @@ -5,11 +5,11 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- Choose Parameter Template Management in the navigation pane on the left, locate the target parameter template, and click View Application Record in the Operation column on the Default Templates page or choose More > View Application Record on the Custom Templates page.
You can view the name or ID of the DB instance to which the parameter template applies, as well as the application status, application time, and failure cause.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- Choose Parameter Templates in the navigation pane on the left, locate the target parameter template, and click View Application Record in the Operation column on the Default Templates page or choose More > View Application Record on the Custom Templates page.
You can view the name or ID of the DB instance to which the parameter template applies, as well as the application status, application time, and failure cause.
In a newly exported or created parameter template, the change history is blank.
Viewing Change History of DB Instance Parameters
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.
You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.
+-Viewing Change History of DB Instance Parameters
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.
You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.
You can apply the parameter template to DB instances as required by referring to Applying a Parameter Template.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0003.html b/docs/gaussdb_mysql/umn/gaussdb_08_0003.html index f3988c8f3..c4351484b 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0003.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0003.html @@ -3,7 +3,7 @@Viewing Change History of a Parameter Template
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
- On the displayed page, choose Change History in the navigation pane on the left.
You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.
+Viewing Change History of a Parameter Template
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- Choose Parameter Templates in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
- On the displayed page, choose Change History in the navigation pane on the left.
You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.
Changing a Security Group
-Scenarios
You can change the security group of a DB instance.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0012.html b/docs/gaussdb_mysql/umn/gaussdb_08_0012.html index e53596225..292975540 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0012.html @@ -4,10 +4,10 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click
in the Security Group field.- To submit the change, click
. - To cancel the change, click
.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click in the Security Group field.
- To submit the change, click .
- To cancel the change, click .
- To submit the change, click
- Click
in the upper right corner on the Basic Information page to view the result of the change. This process takes about 1 to 3 minutes.
- To submit the change, click
-Scenarios
You can compare DB instance parameters with a parameter template that uses the same DB engine to inspect the differences of parameter settings.
You can also compare default parameter templates that use the same DB engine to inspect the differences of parameter settings.
-Comparing Instance Parameters with a Parameter Template
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the displayed page, 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 the settings are the same, no data is displayed.
-Comparing Instance Parameters with a Parameter Template
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the displayed page, 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 the settings are the same, no data is displayed.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0014.html b/docs/gaussdb_mysql/umn/gaussdb_08_0014.html index d00473f6f..2009b7626 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0014.html @@ -5,9 +5,9 @@Comparing Parameter Templates
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
- In the displayed dialog box, select a parameter template that uses the same DB engine as the target template 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 management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
- In the displayed dialog box, select a parameter template that uses the same DB engine as the target template 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.
After the parameter template is replicated, you should wait at least 5 minutes before using it to create a DB instance.
Default parameter templates cannot be replicated. You can create parameter templates based on the default ones.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0015.html b/docs/gaussdb_mysql/umn/gaussdb_08_0015.html index 48465e9c7..dadf7cdca 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0015.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0015.html @@ -3,7 +3,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, click Custom Templates. 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 management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.
Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.
- In the displayed dialog box, configure required details and click OK.
- The template name consists of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, 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 replicated, a new template is generated in the list in the Customer Templates tab of the Parameter Template Management page.
+After the parameter template is replicated, a new template is generated in the list in the Customer Templates tab of the Parameter Templates 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 management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
- Click Yes.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
- Click Yes.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0016.html b/docs/gaussdb_mysql/umn/gaussdb_08_0016.html index c7ed6bba1..6b2bc54e1 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0016.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0016.html @@ -5,7 +5,7 @@- You cannot modify the description of a default parameter template.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0017.html b/docs/gaussdb_mysql/umn/gaussdb_08_0017.html index 10d6dca8d..f32462e30 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0017.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0017.html @@ -5,7 +5,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, click Custom Templates. Locate the parameter template you want to modify 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.
- The description consists of 256 characters but cannot contain the following special characters: >!<"&'=
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, click Custom Templates. Locate the parameter template you want to modify 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.
- The description consists of 256 characters but cannot contain the following special characters: >!<"&'=
- - Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
- Default parameter templates cannot be deleted.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Template Management page, click Custom Templates. Locate the parameter template to be deleted and choose More > Delete in the Operation column.
- In the displayed dialog box, click Yes.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Parameter Templates page, click Custom Templates. Locate the parameter template to be deleted and choose More > Delete in the Operation column.
- In the displayed dialog box, click Yes.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0042.html b/docs/gaussdb_mysql/umn/gaussdb_08_0042.html index 51084af97..3a066a224 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0042.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0042.html @@ -3,7 +3,7 @@Exporting Parameters
-Scenarios
- You can export a parameter template of a DB instance for future use. You can apply the exported parameter template to DB instances by referring to 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 management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.
The parameter template information (parameter names, values, and descriptions) of a DB instance is exported to a CSV file. In the displayed dialog box, enter the file name and click OK. You can export parameter template details (parameter names, values, and descriptions) of an instance to a CSV file for review and analysis.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance.
- In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.
The parameter template information (parameter names, values, and descriptions) of a DB instance is exported to a CSV file. In the displayed dialog box, enter the file name and click OK. You can export parameter template details (parameter names, values, and descriptions) of an instance to a CSV file for review and analysis.
The file name contains 4 to 81 characters and must start with a letter. It can contain only letters, digits, hyphens (-), and underscores (_).
You can change parameter values in custom parameter templates only, but cannot change parameter values in default parameter templates. When you change parameter values in a custom parameter template, the changes take effect for all DB instances to which the parameter template applies.
- GaussDB(for MySQL) has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly and causes a database reboot to fail, you can re-configure the custom parameter template according to the configurations of the default parameter template.
-Modifying Parameter Template Parameters
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates page, click the parameter template you want to view.
- Modify parameters as required.
Available operations are as follows:
+Modifying Parameter Template Parameters
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- In the navigation pane on the left, choose Parameter Templates. On the Custom Templates page, click the parameter template you want to view.
- Modify parameters as required.
Available operations are as follows:
After you modify parameters in a parameter template, some modifications immediately take effect for the DB instance to which the parameter template applies. Exercise caution when performing this operation.
- To save the modifications, click Save.
- To cancel the modifications, click Cancel.
- To preview the modifications, click Preview.
Modifying Instance Parameters
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.
Available operations are as follows:
+Modifying Instance Parameters
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.
Available operations are as follows:
diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html index 2d56558fc..5e30d4bcf 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html @@ -2,7 +2,7 @@ --Check the value in the Effective upon Reboot column.- If the value is Yes and the DB instance status on the Instance Management page is Pending reboot, you must reboot the DB instance for the modifications of this parameter to take effect.
- If the value is No, the modification of this parameter takes effect immediately.
Check the value in the Effective upon Reboot column.- If the value is Yes and the DB instance status on the Instances page is Pending reboot, you must reboot the DB instance for the modifications of this parameter to take effect.
- If the value is No, the modification of this parameter takes effect immediately.
- To save the modifications, click Save.
- To cancel the modifications, click Cancel.
- To preview the modifications, click Preview.
- To save the modifications, click Save.
- To cancel the modifications, click Cancel.
- To preview the modifications, click Preview.
After parameters are modified, you can click Change History to view parameter modification details.
Enabling Read/Write Splitting
Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. This section describes how to enable read/write splitting.
-Procedure
- Log in to the console.
- Click
in the upper left corner and select a region and a project. - Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Database Proxy.Figure 1 Enabling read/write splitting+
Procedure
- Log in to the console.
- Click in the upper left corner and select a region and a project.
- Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Database Proxy.Figure 1 Enabling read/write splitting
- Click Create Proxy Instance.
- In the displayed dialog box, configure required parameters and click OK. After a proxy instance has been created, you can click Create Proxy Instance in the Database Proxy page to add a new proxy instance.
- Proxy Instance Name: Enter 4 to 64 characters starting with a letter. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
- Proxy Mode: Select Read/Write or Read-only.diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0018.html b/docs/gaussdb_mysql/umn/gaussdb_11_0018.html index 9b3b17e96..3a6225720 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_11_0018.html +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0018.html @@ -2,7 +2,7 @@
- Read/Write: All write requests are forwarded only to the primary node, and all read requests are forwarded to the selected nodes based on the read weights. The default read weight of the primary node is 0.
- Read-only: All read requests are forwarded to the selected read replicas based on read weights. Even if the primary node is assigned with a read weight, the weight does not take effect.
- It supports only read requests. If write requests are forwarded to the selected nodes, an error message is displayed.
- This mode offloads the pressure of the primary node by routing all read requests to read replicas.
- DDL, DML, and temporary table operations are not supported in the read-only mode.
Assigning Read Weights
After read/write splitting is enabled, you can assign read weights as required.
-Description
- After read/write splitting is enabled, you can assign read weights for the primary node and read replicas.
- The default read weight of the primary node is 0. The higher read weight the primary node is assigned, the more read requests it can process.
- If the read weight of a read replica is 0, the read replica does not process any read requests.
- The weight of a read replica ranges from 0 to 1000.
- For details about how to assign read weights, see Weight Assignment Rules.
Description
- After read/write splitting is enabled, you can assign read weights for the primary node and read replicas.
- The default read weight of the primary node is 0. The higher read weight the primary node is assigned, the more read requests it can process.
- When the read weights of all nodes are 0, services are not affected. In this case, the primary node processes all read and write requests by default.
- The weight of a read replica ranges from 0 to 1000.
- For details about how to assign read weights, see Weight Assignment Rules.
-Weight Assignment Rules
When the system automatically assigns read weights to read replicas, the weight values are fixed. The default weight equals to the number of vCPUs multiplied by 50. The weight ranges from 100 to 1000.
For example:
@@ -10,7 +10,7 @@Procedure
- Log in to the console.
- Click
in the upper left corner and select a region and a project. - Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
- On the Instance Management page, click the instance name to go to the Basic Information page.
- In the navigation pane on the left, choose Database Proxy. On the displayed page, click the Read/Write Splitting tab.
- In the displayed dialog box, select read replicas for which you want to assign weights on the left and assign the weights on the right.
- Different applications can connect to the instance through the read/write splitting addresses of different proxy instances. Read requests are routed to the proxy instances that applications connect to. You can also add nodes to or remove nodes from proxy instances.
Procedure
- Log in to the console.
- Click in the upper left corner and select a region and a project.
- Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- In the navigation pane on the left, choose Database Proxy. On the displayed page, click the Read/Write Splitting tab.
- In the displayed dialog box, select read replicas for which you want to assign weights on the left and assign the weights on the right.
- Different applications can connect to the instance through the read/write splitting addresses of different proxy instances. Read requests are routed to the proxy instances that applications connect to. You can also add nodes to or remove nodes from proxy instances.
- In the read/write mode, all write requests are routed to the primary node, and read requests are routed to each node based on the read weights.
- In the read-only mode, only read requests can be routed to read replicas based on the read weights. Even if the primary node is assigned with a read weight, the weight does not take effect.
For example, a DB instance contains one primary node and two read replicas, and two proxy instances have been enabled. Proxy instance 1 is in the read/write mode. The primary node and read replica 1 are connected to proxy instance 1 and assigned with a read weight of 100 and 200, respectively. They process read requests in the ratio of 1:2, that is, the primary node processes 1/3 read requests and read replica 1 processes 2/3 read requests. Write requests are automatically routed to the primary node. Proxy instance 2 is in read-only mode. The primary node and read replica 2 are associated with proxy instance 2 and assigned with a read weight of 100 and 200, respectively. In this case, the weight of the primary node does not take effect, and read replica 2 processes all read requests.
Figure 1 Ratio of read requests processed by each node in multiple proxy instancesdiff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0019.html b/docs/gaussdb_mysql/umn/gaussdb_11_0019.html index 9fc0fbdc0..4c4f652f7 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_11_0019.html +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0019.html @@ -2,7 +2,7 @@
Disabling Read/Write Splitting
You can disable read/write splitting as required.
-Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Database Proxy.
- On the Database Proxy page, locate the desired proxy instance and click Disable Database Proxy in the Operation column. In the displayed dialog box, click Yes.
If database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting address are interrupted. You need to switch your applications to the DB instance address.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click GaussDB.
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Database Proxy.
- On the Database Proxy page, locate the desired proxy instance and click Disable Database Proxy in the Operation column. In the displayed dialog box, click Yes.
If database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting address are interrupted. You need to switch your applications to the DB instance address.
- Confirm your specifications.
If you use 0.0.0.0/0, all IP addresses are enabled to access DB instances in the security group.
-Procedure
- Confirm your specifications.