After you create a DB instance, the logical space is the same as the physical space. When a backup starts in a backup chain, the physical space stores the data of the first full backup and subsequent differential backups.
Category
- Full backup: All data is backed up even if no data is updated since the last backup.
- Incremental backup: The system automatically backs up data that has changed since the last automated backup or incremental backup in binlogs every 5 minutes. The binlogs can be used to restore data to a specified point in time.
- Differential backup: The system backs up data that has changed since the most recent full backup or differential backup in to physical files. Physical files cannot be used for log replay.
- Billed space: backup space that you are billed for.
- Logical space: space occupied by full backups.
- Physical space: the amount of data backed up to OBS.
After you create a DB instance, the logical space is the same as the physical space. When a backup starts in a backup chain, the physical space stores the data of the first full backup and subsequent differential backups.
Backup Space Calculation Methods
There is a default backup chain (where there are seven backups). The first automated backup is a full backup, and subsequent automated backups are differential backups.
In a backup chain, the backup space is released only after all full backups and differential backups are deleted.
-
- Logical space: Total size of the logical space – Logical size of the expired backup file
- Physical space: Size of the first full backup file + total size of subsequent differential backup files
- Free space: There is free backup storage up to 100% of your provisioned database storage.
-
Billing is calculated as follows:
-
The system deducts the free space from either the logical space or the physical space, whichever is smaller.
+
The billed space is calculated as follows:
+
- Logical space: Total size of the logical space – Logical size of the expired backup file
- Physical space: Size of the first full backup file + Total size of subsequent differential backup files
- Free space: There is free backup storage up to 100% of storage space.
+
Billed space = Min (Logical space, Physical space) – Free space = Min (Logical space, Physical space) – Storage space
-
Example
A backup line contains seven backups by default. There are 11 backups shown in the following figure. The 1st backup to the 7th belong to one backup line and the 8th to the 11th belong to another.
+
Example
A backup chain contains seven backups by default. There are 11 backups shown in the following figure. The 1st backup to the 7th belong to one backup chain and the 8th to the 11th belong to the other backup chain.
Figure 1 Backup example
If there is 1,000 MB of backup space and the logical space is 1,000 MB each time, the physical space for the 1st backup is 1,000 MB. If the incremental data size is 100 MB each time, the physical space for the 2nd backup to 7th is 100 MB.
-
A backup line contains seven backups by default. The physical space for the 8th backup is 1,000 MB because it represents a new backup line.
+
A backup chain contains seven backups by default. The physical space for the 8th backup is 1,000 MB because it represents a new backup chain.
Billed space includes the space of the two chains in the example.
Suppose that after the 11th backup was created, and the 1st, 2nd and 3rd backups expired and were automatically deleted. The size of each space is calculated as follows:
-
- Total logical space size = Total logical space size – Logical size of the expired backup file (1,000 MB x 11 - 3,000 MB = 8,000 MB in this example).
- Physical space: size of data backed up to OBS. In this example, physical space includes the sum of physical space on the two backup links: 1,000 MB + (100 MB x 6) +1,000 MB+ (100 MB X 3) =2,900 MB
- Total billed space = Min (Total size of logical space, Total size of physical space) – free space, so the total billed space in this example = Min (8,000 MB, 2,900 MB) – 1,000 MB = 1,900 MB
+
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0072.html b/docs/gaussdb_mysql/umn/gaussdb_03_0072.html
index b01f93da..c01e35b5 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0072.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0072.html
@@ -8,7 +8,7 @@
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.
-
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 Databases, click GaussDB(for MySQL).
- 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: >!<"&'=
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html
index e150f6c0..2239b475 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 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:
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0092.html b/docs/gaussdb_mysql/umn/gaussdb_03_0092.html
index 73819d00..3131d0c7 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0092.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0092.html
@@ -6,7 +6,7 @@
- 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 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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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 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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0111.html b/docs/gaussdb_mysql/umn/gaussdb_03_0111.html
index 7685930a..dd1201fd 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0111.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0111.html
@@ -5,7 +5,7 @@
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.
-
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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0112.html b/docs/gaussdb_mysql/umn/gaussdb_03_0112.html
index 198d8eec..507655c2 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0112.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0112.html
@@ -2,7 +2,7 @@
Managing a Read Replica
You can manage read replicas after they are created, such as promoting a read replica to the primary node and delete a read replica.
-
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.
- Click the target DB instance to go to the Basic Information page.
- At the bottom of the Basic Information page, you can view and manage all read replicas associated with the DB 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 Databases, click GaussDB(for MySQL).
- Click the target DB instance to go to the Basic Information page.
- At the bottom of the Basic Information page, you can view and manage all read replicas associated with the DB instance.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0113.html b/docs/gaussdb_mysql/umn/gaussdb_03_0113.html
index acf5854a..ab676fc6 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0113.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0113.html
@@ -2,7 +2,7 @@
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 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.
+
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 Databases, click GaussDB(for MySQL).
- 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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0114.html b/docs/gaussdb_mysql/umn/gaussdb_03_0114.html
index 64993561..99dfcaea 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0114.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0114.html
@@ -7,7 +7,7 @@
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 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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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_03_0132.html b/docs/gaussdb_mysql/umn/gaussdb_03_0132.html
index c7b8b97b..b6236bed 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0132.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0132.html
@@ -3,7 +3,7 @@
Changing an Instance Description
Scenarios
After an instance is created, you can add a description.
-
Procedure
- Log in to the management console.
- Click
in the upper left corner and select a region and a project. - Click
in the upper left corner of the page and choose Databases > GaussDB. In the navigation pane on the left, click GaussDB(for MySQL). - On the Instances page, locate the instance that you want to edit the description for and click
in the Description column to edit the instance description. Then, click OK.Alternatively, click the instance name to go to the Basic Information page. In the DB Instance Information area, click in the Description field to edit the instance description.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the instance that you want to edit the description for and click in the Description column to edit the instance description. Then, click OK.
Alternatively, click the instance name to go to the Basic Information page. In the DB Instance Information area, click in the Description field to edit the instance description.
The instance description can contain up to 64 characters, and cannot start with and end with a space. Only letters, digits, hyphens (-), underscores (_), periods (.), and spaces are allowed.
- To submit the change, click
. - To cancel the change, click
.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0152.html b/docs/gaussdb_mysql/umn/gaussdb_03_0152.html
index 84e69784..79d2cb1f 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0152.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0152.html
@@ -3,12 +3,12 @@
Enabling or Disabling SQL Explorer
Enabling SQL Explorer will allow GaussDB(for MySQL) to store all SQL statement logs for analysis.
By default, SQL Explorer is disabled for GaussDB(for MySQL). This section describes how to enable and disable SQL Explorer.
-
Enabling SQL Explorer
- 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 Advanced O&M.
- In the SQL Explorer tab, set
to 
. In the displayed dialog box, select I have read the agreement and agree to having my data stored, and click OK.Figure 1 Enabling SQL Explorer
+
-
diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0015.html b/docs/gaussdb_mysql/umn/gaussdb_05_0015.html
new file mode 100644
index 00000000..0c620b88
--- /dev/null
+++ b/docs/gaussdb_mysql/umn/gaussdb_05_0015.html
@@ -0,0 +1,18 @@
+
+
+
Granting Database Permissions
+
Scenarios
You can grant permissions to database users you have created to use specific databases or revoke permissions from specific database users.
+
+
Constraints
This operation is not allowed for DB instances that are being restored.
+
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance.
- In the navigation pane, choose Databases. On the displayed page, locate the target database and click Authorize in the Operation column.
- In the displayed dialog box, select one or more unauthorized database users and click OK.
If no users are available, you can create one by referring to Creating a Database Account.
+
+
+
+
+
+
diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0018.html b/docs/gaussdb_mysql/umn/gaussdb_05_0018.html
index 217d26a6..5f086093 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 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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0098.html b/docs/gaussdb_mysql/umn/gaussdb_05_0098.html
index 7c999437..91c6f691 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_05_0098.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_05_0098.html
@@ -3,7 +3,7 @@
Viewing Application Records of a Parameter Template
Scenarios
You can view the application records of a parameter template.
-
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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0099.html b/docs/gaussdb_mysql/umn/gaussdb_05_0099.html
index 5d652556..2444a973 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_05_0099.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_05_0099.html
@@ -5,11 +5,11 @@
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 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.
+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 Databases, click GaussDB(for MySQL).
- 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.
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.
+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 Databases, click GaussDB(for MySQL).
- 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.
Modifying Database Remarks
+Scenarios
GaussDB(for MySQL) allows you to modify remarks of created databases.
+
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance.
- In the navigation pane, choose Databases.
- Locate the target database and click
in the Remarks column. The database remarks can be empty or contain up to 512 characters.
+
+
+
+
Upgrading the Minor Version of a DB Instance
-Scenario
GaussDB(for MySQL) supports manual minor version upgrades, which can improve performance, add new functions, and fix bugs.
+
Scenarios
GaussDB(for MySQL) supports manual minor version upgrades, which can improve performance, add new functions, and fix bugs.
Precautions
- The upgrade will cause the instance to reboot and briefly interrupt services. To limit the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
- If an instance contains a large number of table partitions (more than 1 million), it may take more than 2 hours to reboot the instance.
- If the primary node and read replicas of an instance are deployed in the same AZ, a minor version upgrade will trigger a failover. If they are in different AZs, a minor version upgrade will trigger two failovers. A failover means that the system fails over to a read replica in case the primary node is unavailable.
- When you upgrade a minor version of an instance, minor versions of read replicas (if any) will also be upgraded automatically. Minor versions of read replicas cannot be upgraded separately. A minor version upgrade cannot be rolled back after the upgrade is complete.
- DDL operations, such as CREATE EVENT, DROP EVENT, and ALTER EVENT, are not allowed during a minor version upgrade.
-
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click
in the upper left corner of the page and choose Database > 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 DB Instance Information area, click Upgrade in the DB Engine Version field.
- In the displayed dialog box, select a scheduled time and click OK.
Upon submission: The system upgrades the minor version immediately after your submission of the upgrade request. After the operation is complete, in the Task Center page, click Instant Tasks and view the information about the upgrade task.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target instance to go to the Basic Information page.
- In the DB Instance Information area, click Upgrade in the DB Engine Version field.
- In the displayed dialog box, select a scheduled time and click OK.
Upon submission: The system upgrades the minor version immediately after your submission of the upgrade request. After the operation is complete, in the Task Center page, click Instant Tasks and view the information about the upgrade task.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0003.html b/docs/gaussdb_mysql/umn/gaussdb_08_0003.html
index c4351484..c4c9b436 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_08_0003.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_08_0003.html
@@ -3,7 +3,7 @@
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 29297554..b2494556 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_08_0012.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_08_0012.html
@@ -4,10 +4,10 @@
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 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.
+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 Databases, click GaussDB(for MySQL).
- 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.
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.
+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 Databases, click GaussDB(for MySQL).
- 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.
-
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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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 Templates page.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0015.html b/docs/gaussdb_mysql/umn/gaussdb_08_0015.html
index dadf7cdc..d61b0d2f 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_08_0015.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_08_0015.html
@@ -3,7 +3,7 @@
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 Templates 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 Databases, click GaussDB(for MySQL).
- 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 6b2bc54e..f8b6bc1c 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 f32462e3..a39a164c 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_08_0017.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_08_0017.html
@@ -5,7 +5,7 @@
- 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 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.
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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 3a066a22..874f8cf3 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 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.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- 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 (_).
diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0112.html b/docs/gaussdb_mysql/umn/gaussdb_08_0112.html
index 47ff76d5..8c908ab6 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_08_0112.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_08_0112.html
@@ -5,7 +5,7 @@
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 Templates. 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 Databases, click GaussDB(for MySQL).
- 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.
@@ -16,7 +16,7 @@
-
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:
+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 Databases, 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 Parameters. On the displayed page, modify parameters as required.
Available operations are as follows:
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.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html
index 5e30d4bc..c039c249 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html
@@ -1,9 +1,8 @@
-
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 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.
- 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.
+Creating a Proxy Instance
+A proxy instance enables read and write requests to be automatically routed through its IP address. This section describes how to create a proxy instance.
+
