diff --git a/docs/gaussdb_mysql/umn/.placeholder b/docs/gaussdb_mysql/umn/.placeholder deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/gaussdb_mysql/umn/ALL_META.TXT.json b/docs/gaussdb_mysql/umn/ALL_META.TXT.json index da7e7ec3..9c2142bc 100644 --- a/docs/gaussdb_mysql/umn/ALL_META.TXT.json +++ b/docs/gaussdb_mysql/umn/ALL_META.TXT.json @@ -53,10 +53,10 @@ "uri":"gaussdb_01_0004.html", "product_code":"gaussdb", "code":"6", - "des":"GaussDB(for MySQL) instance classes are listed in the following table and vary according to actual situations.", + "des":"GaussDB(for MySQL) instance specifications are listed in the following table and vary according to actual situations.", "doc_type":"usermanual", - "kw":"DB Instance Classes,DB Instance Description,User Guide", - "title":"DB Instance Classes", + "kw":"DB Instance Specifications,DB Instance Description,User Guide", + "title":"DB Instance Specifications", "githuburl":"" }, { @@ -263,7 +263,7 @@ "uri":"gaussdb_03_0007.html", "product_code":"gaussdb", "code":"27", - "des":"GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through an ECS or EIP.Prepare an ECS in the same VPC subnet as GaussDB(for MySQL) or p", + "des":"GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through a private network or EIP.Prepare an ECS in the same VPC subnet as GaussDB(for ", "doc_type":"usermanual", "kw":"Migrating Data to GaussDB(for MySQL) Using mysqldump,Data Migration,User Guide", "title":"Migrating Data to GaussDB(for MySQL) Using mysqldump", @@ -275,8 +275,8 @@ "code":"28", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Database Connections", - "title":"Database Connections", + "kw":"Connection Management", + "title":"Connection Management", "githuburl":"" }, { @@ -285,7 +285,7 @@ "code":"29", "des":"By default, a GaussDB(for MySQL) DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to the DB instance for public acc", "doc_type":"usermanual", - "kw":"configure security group rules,Binding and Unbinding an EIP,Database Connections,User Guide", + "kw":"configure security group rules,Binding and Unbinding an EIP,Connection Management,User Guide", "title":"Binding and Unbinding an EIP", "githuburl":"" }, @@ -293,76 +293,176 @@ "uri":"gaussdb_03_0012.html", "product_code":"gaussdb", "code":"30", - "des":"You can change the database port of a GaussDB(for MySQL) DB instance. The change applies to the ports of the primary node and read replicas, and may affect services inter", + "des":"You can change the database port of a GaussDB(for MySQL) instance. The change applies to the ports of the primary node and read replicas, and may affect services intermit", "doc_type":"usermanual", - "kw":"change the database port,Changing a Database Port,Database Connections,User Guide", + "kw":"change the database port,Changing a Database Port,Connection Management,User Guide", "title":"Changing a Database Port", "githuburl":"" }, + { + "uri":"gaussdb_11_0050.html", + "product_code":"gaussdb", + "code":"31", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Proxy (Read/Write Splitting)", + "title":"Database Proxy (Read/Write Splitting)", + "githuburl":"" + }, + { + "uri":"gaussdb_02_0011.html", + "product_code":"gaussdb", + "code":"32", + "des":"Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read rep", + "doc_type":"usermanual", + "kw":"Introducing Read/Write Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Introducing Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"gaussdb_11_0017.html", + "product_code":"gaussdb", + "code":"33", + "des":"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 sp", + "doc_type":"usermanual", + "kw":"Enabling Read/Write Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Enabling Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"gaussdb_11_0031.html", + "product_code":"gaussdb", + "code":"34", + "des":"After read/write splitting is enabled, you can change the read/write splitting address.Changing the read/write splitting address will interrupt database connections and s", + "doc_type":"usermanual", + "kw":"change the read/write splitting address,Changing the Read/Write Splitting Address,Database Proxy (Re", + "title":"Changing the Read/Write Splitting Address", + "githuburl":"" + }, + { + "uri":"gaussdb_11_0018.html", + "product_code":"gaussdb", + "code":"35", + "des":"After read/write splitting is enabled, you can assign read weights as required.After read/write splitting is enabled, you can assign read weights for the primary node and", + "doc_type":"usermanual", + "kw":"Assigning Read Weights,Database Proxy (Read/Write Splitting),User Guide", + "title":"Assigning Read Weights", + "githuburl":"" + }, + { + "uri":"gaussdb_11_0025.html", + "product_code":"gaussdb", + "code":"36", + "des":"If load balancing is enabled for a database proxy instance, the security group associated with the proxy instance does not apply. You need to use access control to grant ", + "doc_type":"usermanual", + "kw":"Enabling or Disabling Access Control,Database Proxy (Read/Write Splitting),User Guide", + "title":"Enabling or Disabling Access Control", + "githuburl":"" + }, + { + "uri":"gaussdb_11_0019.html", + "product_code":"gaussdb", + "code":"37", + "des":"You can disable read/write splitting as required.If database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting address ", + "doc_type":"usermanual", + "kw":"Disabling Read/Write Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Disabling Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"gaussdb_11_0021.html", + "product_code":"gaussdb", + "code":"38", + "des":"After read/write splitting is enabled, databases can be connected through a read/write splitting address. You can use internal SQL commands to verify the read/write split", + "doc_type":"usermanual", + "kw":"Testing Read/Write Splitting Performance,Database Proxy (Read/Write Splitting),User Guide", + "title":"Testing Read/Write Splitting Performance", + "githuburl":"" + }, { "uri":"gaussdb_03_0029.html", "product_code":"gaussdb", - "code":"31", + "code":"39", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"DB Instance Management", - "title":"DB Instance Management", + "kw":"Instance Modifications", + "title":"Instance Modifications", "githuburl":"" }, { "uri":"gaussdb_03_0032.html", "product_code":"gaussdb", - "code":"32", + "code":"40", "des":"You can change the name of a GaussDB(for MySQL) DB instance.The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lower", "doc_type":"usermanual", - "kw":"Changing a DB Instance Name,DB Instance Management,User Guide", + "kw":"Changing a DB Instance Name,Instance Modifications,User Guide", "title":"Changing a DB Instance Name", "githuburl":"" }, + { + "uri":"gaussdb_03_0132.html", + "product_code":"gaussdb", + "code":"41", + "des":"After an instance is created, you can add a description.Alternatively, click the instance name to go to the Basic Information page. In the DB Instance Information area, c", + "doc_type":"usermanual", + "kw":"Changing an Instance Description,Instance Modifications,User Guide", + "title":"Changing an Instance Description", + "githuburl":"" + }, { "uri":"gaussdb_03_0092.html", "product_code":"gaussdb", - "code":"33", - "des":"You can change the CPU or memory (instance class) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "code":"42", + "des":"You can change the vCPUs or memory of a DB instance as required. If the status of a DB instance changes from Changing instance specifications to Available, the change is ", "doc_type":"usermanual", - "kw":"CPU or memory,Changing a DB Instance Class,DB Instance Management,User Guide", - "title":"Changing a DB Instance Class", + "kw":"vCPUs or memory,Changing vCPUs and Memory of an Instance,Instance Modifications,User Guide", + "title":"Changing vCPUs and Memory of an Instance", "githuburl":"" }, { "uri":"gaussdb_03_0040.html", "product_code":"gaussdb", - "code":"34", + "code":"43", "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, you must reboot the DB instance for the modifications to take effec", "doc_type":"usermanual", - "kw":"Rebooting a DB Instance,DB Instance Management,User Guide", + "kw":"Rebooting a DB Instance,Instance Modifications,User Guide", "title":"Rebooting a DB Instance", "githuburl":"" }, { "uri":"gaussdb_03_0045.html", "product_code":"gaussdb", - "code":"35", + "code":"44", "des":"You can export a DB instance list (containing all or selected DB instances) to view and analyze DB instance information.", "doc_type":"usermanual", - "kw":"export a DB instance,Exporting DB Instance Information,DB Instance Management,User Guide", + "kw":"export a DB instance,Exporting DB Instance Information,Instance Modifications,User Guide", "title":"Exporting DB Instance Information", "githuburl":"" }, { "uri":"gaussdb_03_0047.html", "product_code":"gaussdb", - "code":"36", + "code":"45", "des":"You can manually delete a DB instance on the Instance Management page.If you delete a DB instance, the read replicas associated with it are also deleted.Deleted DB instan", "doc_type":"usermanual", - "kw":"Procedure,Deleting a DB Instance,DB Instance Management,User Guide", + "kw":"Procedure,Deleting a DB Instance,Instance Modifications,User Guide", "title":"Deleting a DB Instance", "githuburl":"" }, + { + "uri":"gaussdb_05_2265.html", + "product_code":"gaussdb", + "code":"46", + "des":"GaussDB(for MySQL) supports manual minor version upgrades, which can improve performance, add new functions, and fix bugs.The upgrade will cause the instance to reboot an", + "doc_type":"usermanual", + "kw":"Upgrading the Minor Version of a DB Instance,Instance Modifications,User Guide", + "title":"Upgrading the Minor Version of a DB Instance", + "githuburl":"" + }, { "uri":"gaussdb_03_0009.html", "product_code":"gaussdb", - "code":"37", + "code":"47", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Read Replicas", @@ -372,7 +472,7 @@ { "uri":"gaussdb_03_0110.html", "product_code":"gaussdb", - "code":"38", + "code":"48", "des":"Currently, DB instances support read replicas.In read-intensive scenarios, a primary node may be unable to handle the read pressure and service performance may be affecte", "doc_type":"usermanual", "kw":"Introducing Read Replicas,Read Replicas,User Guide", @@ -382,7 +482,7 @@ { "uri":"gaussdb_03_0111.html", "product_code":"gaussdb", - "code":"39", + "code":"49", "des":"Read replicas are used to enhance the read capabilities and reduce read pressure on DB instances.After a DB instance is created, you can create read replicas for it.If yo", "doc_type":"usermanual", "kw":"create read replicas,Creating a Read Replica,Read Replicas,User Guide", @@ -392,7 +492,7 @@ { "uri":"gaussdb_03_0112.html", "product_code":"gaussdb", - "code":"40", + "code":"50", "des":"You can manage read replicas after they are created, such as promoting a read replica to the primary node and delete a read replica.", "doc_type":"usermanual", "kw":"Managing a Read Replica,Read Replicas,User Guide", @@ -402,7 +502,7 @@ { "uri":"gaussdb_03_0113.html", "product_code":"gaussdb", - "code":"41", + "code":"51", "des":"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 t", "doc_type":"usermanual", "kw":"Promoting a Read Replica to the Primary Node,Read Replicas,User Guide", @@ -412,7 +512,7 @@ { "uri":"gaussdb_03_0114.html", "product_code":"gaussdb", - "code":"42", + "code":"52", "des":"You can manually delete read replicas on the Instance Management page.Deleted read replicas cannot be restored. Exercise caution when performing this operation.You can de", "doc_type":"usermanual", "kw":"Procedure,Deleting a Read Replica,Read Replicas,User Guide", @@ -422,7 +522,7 @@ { "uri":"gaussdb_03_0050.html", "product_code":"gaussdb", - "code":"43", + "code":"53", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Security", @@ -432,7 +532,7 @@ { "uri":"gaussdb_03_0051.html", "product_code":"gaussdb", - "code":"44", + "code":"54", "des":"You can reset the administrator password of a DB instance.You can also reset the password of your database account when using GaussDB(for MySQL).You cannot reset the admi", "doc_type":"usermanual", "kw":"reset the administrator password,Resetting the Administrator Password,Data Security,User Guide", @@ -442,7 +542,7 @@ { "uri":"gaussdb_08_0003.html", "product_code":"gaussdb", - "code":"45", + "code":"55", "des":"You can change the security group of a DB instance.To submit the change, click .To cancel the change, click .", "doc_type":"usermanual", "kw":"Changing a Security Group,Data Security,User Guide", @@ -452,7 +552,7 @@ { "uri":"gaussdb_03_0055.html", "product_code":"gaussdb", - "code":"46", + "code":"56", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backups and Restorations", @@ -462,7 +562,7 @@ { "uri":"gaussdb_03_0056.html", "product_code":"gaussdb", - "code":"47", + "code":"57", "des":"GaussDB(for MySQL) supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window of your DB instances. GaussDB(", "doc_type":"usermanual", "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", @@ -472,7 +572,7 @@ { "uri":"gaussdb_03_0058.html", "product_code":"gaussdb", - "code":"48", + "code":"58", "des":"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 inst", "doc_type":"usermanual", "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", @@ -482,7 +582,7 @@ { "uri":"gaussdb_03_0063.html", "product_code":"gaussdb", - "code":"49", + "code":"59", "des":"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.The Create New Instance p", "doc_type":"usermanual", "kw":"Restoring Data from a Backup,Backups and Restorations,User Guide", @@ -492,7 +592,7 @@ { "uri":"gaussdb_03_0068.html", "product_code":"gaussdb", - "code":"50", + "code":"60", "des":"You can delete manual backups to release storage space.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups c", "doc_type":"usermanual", "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", @@ -502,7 +602,7 @@ { "uri":"gaussdb_08_0011.html", "product_code":"gaussdb", - "code":"51", + "code":"61", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Parameter Template Management", @@ -512,7 +612,7 @@ { "uri":"gaussdb_03_0072.html", "product_code":"gaussdb", - "code":"52", + "code":"62", "des":"You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be", "doc_type":"usermanual", "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", @@ -522,7 +622,7 @@ { "uri":"gaussdb_08_0112.html", "product_code":"gaussdb", - "code":"53", + "code":"63", "des":"You can modify parameters in a custom parameter template to optimize GaussDB(for MySQL) database performance.You can change parameter values in custom parameter templates", "doc_type":"usermanual", "kw":"Modifying a Parameter Template,Parameter Template Management,User Guide", @@ -532,18 +632,18 @@ { "uri":"gaussdb_08_0042.html", "product_code":"gaussdb", - "code":"54", + "code":"64", "des":"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 Te", "doc_type":"usermanual", - "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", - "title":"Exporting a Parameter Template", + "kw":"Exporting Parameters,Parameter Template Management,User Guide", + "title":"Exporting Parameters", "githuburl":"" }, { "uri":"gaussdb_08_0012.html", "product_code":"gaussdb", - "code":"55", - "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "code":"65", + "des":"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 defaul", "doc_type":"usermanual", "kw":"Compare,Comparing a Parameter Template,Parameter Template Management,User Guide", "title":"Comparing a Parameter Template", @@ -552,7 +652,7 @@ { "uri":"gaussdb_05_0099.html", "product_code":"gaussdb", - "code":"56", + "code":"66", "des":"You can view the change history of DB instance parameters or custom parameter templates.In a newly exported or created parameter template, the change history is blank.You", "doc_type":"usermanual", "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", @@ -562,7 +662,7 @@ { "uri":"gaussdb_08_0014.html", "product_code":"gaussdb", - "code":"57", + "code":"67", "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", "doc_type":"usermanual", "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", @@ -572,8 +672,8 @@ { "uri":"gaussdb_08_0015.html", "product_code":"gaussdb", - "code":"58", - "des":"You can reset all parameters in a custom parameter template to their default settings.After you reset a parameter template, click the DB instance to which the parameter t", + "code":"68", + "des":"You can reset all parameters in a custom parameter template to their default settings.", "doc_type":"usermanual", "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", "title":"Resetting a Parameter Template", @@ -582,7 +682,7 @@ { "uri":"gaussdb_05_0018.html", "product_code":"gaussdb", - "code":"59", + "code":"69", "des":"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_poo", "doc_type":"usermanual", "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", @@ -592,7 +692,7 @@ { "uri":"gaussdb_05_0098.html", "product_code":"gaussdb", - "code":"60", + "code":"70", "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance to which the parameter template applies, as well as the applic", "doc_type":"usermanual", "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", @@ -602,7 +702,7 @@ { "uri":"gaussdb_08_0016.html", "product_code":"gaussdb", - "code":"61", + "code":"71", "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.After you submit the modificatio", "doc_type":"usermanual", "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", @@ -612,8 +712,8 @@ { "uri":"gaussdb_08_0017.html", "product_code":"gaussdb", - "code":"62", - "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "code":"72", + "des":"You can delete a custom parameter template that is no longer needed.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", "doc_type":"usermanual", "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", "title":"Deleting a Parameter Template", @@ -622,8 +722,8 @@ { "uri":"gaussdb_03_0082.html", "product_code":"gaussdb", - "code":"63", - "des":"GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:Consist of at least eight characters.Contain at least one uppercase let", + "code":"73", + "des":"GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:Consist of at least eight characters.Contain at least three types of th", "doc_type":"usermanual", "kw":"Database Security,Working with GaussDB(for MySQL),User Guide", "title":"Database Security", @@ -632,7 +732,7 @@ { "uri":"gaussdb_03_0083.html", "product_code":"gaussdb", - "code":"64", + "code":"74", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring", @@ -642,7 +742,7 @@ { "uri":"gaussdb_03_0085.html", "product_code":"gaussdb", - "code":"65", + "code":"75", "des":"You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of monitoring metrics to be reporte", "doc_type":"usermanual", "kw":"Cloud Eye,Configuring Displayed Metrics,Monitoring,User Guide", @@ -652,7 +752,7 @@ { "uri":"gaussdb_03_0087.html", "product_code":"gaussdb", - "code":"66", + "code":"76", "des":"You can set alarm rules for GaussDB(for MySQL) to customize the monitored objects and notification policies and stay aware of the GaussDB(for MySQL) operating status.The ", "doc_type":"usermanual", "kw":"set alarm rules,alarm rule,Setting Alarm Rules,Monitoring,User Guide", @@ -662,7 +762,7 @@ { "uri":"gaussdb_03_0088.html", "product_code":"gaussdb", - "code":"67", + "code":"77", "des":"The Cloud Eye service monitors operating statuses of DB instances. You can view the monitoring metrics of DB instances on the management console. By monitoring system res", "doc_type":"usermanual", "kw":"Cloud Eye,Viewing Monitoring Metrics,Monitoring,User Guide", @@ -672,7 +772,7 @@ { "uri":"gaussdb_03_0013.html", "product_code":"gaussdb", - "code":"68", + "code":"78", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Interconnection with CTS", @@ -682,7 +782,7 @@ { "uri":"gaussdb_03_0014.html", "product_code":"gaussdb", - "code":"69", + "code":"79", "des":"Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for further querying, auditing, and backtracking. Table 1 lists the supported operations.", "doc_type":"usermanual", "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", @@ -692,7 +792,7 @@ { "uri":"gaussdb_03_0015.html", "product_code":"gaussdb", - "code":"70", + "code":"80", "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", "doc_type":"usermanual", "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", @@ -702,7 +802,7 @@ { "uri":"gaussdb_03_0016.html", "product_code":"gaussdb", - "code":"71", + "code":"81", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Logs", @@ -712,7 +812,7 @@ { "uri":"gaussdb_03_0017.html", "product_code":"gaussdb", - "code":"72", + "code":"82", "des":"You can view database logs on the GaussDB console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.", "doc_type":"usermanual", "kw":"Viewing Logs,Logs,User Guide", @@ -722,7 +822,7 @@ { "uri":"gaussdb_03_0018.html", "product_code":"gaussdb", - "code":"73", + "code":"83", "des":"GaussDB(for MySQL) log management allows you to view database-level logs, including error logs and slow SQL query logs.Error logs in different time periodsError logs of t", "doc_type":"usermanual", "kw":"Viewing Error Logs,Logs,User Guide", @@ -732,17 +832,57 @@ { "uri":"gaussdb_03_0019.html", "product_code":"gaussdb", - "code":"74", + "code":"84", "des":"Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details and statistics to identify the statements that are executing", "doc_type":"usermanual", "kw":"Viewing Slow Query Logs,Logs,User Guide", "title":"Viewing Slow Query Logs", "githuburl":"" }, + { + "uri":"gaussdb_03_0152.html", + "product_code":"gaussdb", + "code":"85", + "des":"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", + "doc_type":"usermanual", + "kw":"Enabling or Disabling SQL Explorer,Logs,User Guide", + "title":"Enabling or Disabling SQL Explorer", + "githuburl":"" + }, + { + "uri":"gaussdb_05_0007.html", + "product_code":"gaussdb", + "code":"86", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Task Center", + "title":"Task Center", + "githuburl":"" + }, + { + "uri":"gaussdb_task_0001.html", + "product_code":"gaussdb", + "code":"87", + "des":"You can view the progresses and results of tasks on the Task Center page.You can view and manage the following tasks:Creating a DB instanceRebooting a DB instanceDeleting", + "doc_type":"usermanual", + "kw":"Viewing a Task,Task Center,User Guide", + "title":"Viewing a Task", + "githuburl":"" + }, + { + "uri":"gaussdb_task_0002.html", + "product_code":"gaussdb", + "code":"88", + "des":"You can delete the task records no longer need to be displayed. The deletion only deletes the task records, and does not delete the DB instances or terminate the tasks th", + "doc_type":"usermanual", + "kw":"Deleting a Task Record,Task Center,User Guide", + "title":"Deleting a Task Record", + "githuburl":"" + }, { "uri":"gaussdb_faq.html", "product_code":"gaussdb", - "code":"75", + "code":"89", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -752,7 +892,7 @@ { "uri":"gaussdb_faq_0002.html", "product_code":"gaussdb", - "code":"76", + "code":"90", "des":"GaussDB(for MySQL) supports the decoupling of compute and storage, improving your experience in terms of high availability, backup and restoration, upgrade and capacity e", "doc_type":"usermanual", "kw":"GaussDB(for MySQL),Does GaussDB(for MySQL) Support Compute and Storage Decoupling?,FAQs,User Guide", @@ -762,7 +902,7 @@ { "uri":"gaussdb_faq_0003.html", "product_code":"gaussdb", - "code":"77", + "code":"91", "des":"GaussDB(for MySQL) supports up to 128 TB of data and can easily handle large amounts of data requests.", "doc_type":"usermanual", "kw":"GaussDB(for MySQL),What's the Maximum Data Volume Supported by GaussDB(for MySQL)?,FAQs,User Guide", @@ -772,7 +912,7 @@ { "uri":"gaussdb_faq_0005.html", "product_code":"gaussdb", - "code":"78", + "code":"92", "des":"During the creation of a GaussDB(for MySQL) DB instance, a read replica is created by default in addition to a primary node. If the primary node fails, the system automat", "doc_type":"usermanual", "kw":"Does GaussDB(for MySQL) Support Automatic Failover?,FAQs,User Guide", @@ -782,7 +922,7 @@ { "uri":"gaussdb_faq_0006.html", "product_code":"gaussdb", - "code":"79", + "code":"93", "des":"If you modify the parameters in a parameter template, but the modifications do not take effect, you may need to reboot the DB instance associated with the parameter templ", "doc_type":"usermanual", "kw":"What Should I Do When Modifications to GaussDB(for MySQL) Instance Parameters Does Not Take Effect?,", @@ -792,7 +932,7 @@ { "uri":"gaussdb_faq_0007.html", "product_code":"gaussdb", - "code":"80", + "code":"94", "des":"You can create a maximum of 15 read replicas for a GaussDB(for MySQL) DB instance.", "doc_type":"usermanual", "kw":"GaussDB(for MySQL),How Many Read Replicas Can I Create for a GaussDB(for MySQL) DB Instance?,FAQs,Us", @@ -802,7 +942,7 @@ { "uri":"gaussdb_faq_0011.html", "product_code":"gaussdb", - "code":"81", + "code":"95", "des":"MySQL provides client installation packages for different OSs on its official website. Click here to download the MySQL 8.0 client installation package or click here to d", "doc_type":"usermanual", "kw":"How Can I Install the MySQL Client?,FAQs,User Guide", @@ -812,7 +952,7 @@ { "uri":"gaussdb_faq_0010.html", "product_code":"gaussdb", - "code":"82", + "code":"96", "des":"Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.On the displayed console, choose File > Add/Remove Snap-in.In the left Available sn", "doc_type":"usermanual", "kw":"How Can I Import the Root Certificate to a Windows or Linux OS?,FAQs,User Guide", @@ -822,7 +962,7 @@ { "uri":"gaussdb_faq_0009.html", "product_code":"gaussdb", - "code":"83", + "code":"97", "des":"Perform the following steps to identify the problem:If they are in the same VPC, go to 2.If they are in different VPCs, create an ECS in the VPC where the DB instance is ", "doc_type":"usermanual", "kw":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) DB Instance?,FAQs,User Guide", @@ -832,7 +972,7 @@ { "uri":"change_history.html", "product_code":"gaussdb", - "code":"84", + "code":"98", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", diff --git a/docs/gaussdb_mysql/umn/CLASS.TXT.json b/docs/gaussdb_mysql/umn/CLASS.TXT.json index 55b89cdf..6577c037 100644 --- a/docs/gaussdb_mysql/umn/CLASS.TXT.json +++ b/docs/gaussdb_mysql/umn/CLASS.TXT.json @@ -45,9 +45,9 @@ "code":"5" }, { - "desc":"GaussDB(for MySQL) instance classes are listed in the following table and vary according to actual situations.", + "desc":"GaussDB(for MySQL) instance specifications are listed in the following table and vary according to actual situations.", "product_code":"gaussdb", - "title":"DB Instance Classes", + "title":"DB Instance Specifications", "uri":"gaussdb_01_0004.html", "doc_type":"usermanual", "p_code":"5", @@ -234,7 +234,7 @@ "code":"26" }, { - "desc":"GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through an ECS or EIP.Prepare an ECS in the same VPC subnet as GaussDB(for MySQL) or p", + "desc":"GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through a private network or EIP.Prepare an ECS in the same VPC subnet as GaussDB(for ", "product_code":"gaussdb", "title":"Migrating Data to GaussDB(for MySQL) Using mysqldump", "uri":"gaussdb_03_0007.html", @@ -245,7 +245,7 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"gaussdb", - "title":"Database Connections", + "title":"Connection Management", "uri":"gaussdb_03_0010.html", "doc_type":"usermanual", "p_code":"25", @@ -261,7 +261,7 @@ "code":"29" }, { - "desc":"You can change the database port of a GaussDB(for MySQL) DB instance. The change applies to the ports of the primary node and read replicas, and may affect services inter", + "desc":"You can change the database port of a GaussDB(for MySQL) instance. The change applies to the ports of the primary node and read replicas, and may affect services intermit", "product_code":"gaussdb", "title":"Changing a Database Port", "uri":"gaussdb_03_0012.html", @@ -272,29 +272,110 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"gaussdb", - "title":"DB Instance Management", - "uri":"gaussdb_03_0029.html", + "title":"Database Proxy (Read/Write Splitting)", + "uri":"gaussdb_11_0050.html", "doc_type":"usermanual", "p_code":"25", "code":"31" }, + { + "desc":"Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read rep", + "product_code":"gaussdb", + "title":"Introducing Read/Write Splitting", + "uri":"gaussdb_02_0011.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"32" + }, + { + "desc":"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 sp", + "product_code":"gaussdb", + "title":"Enabling Read/Write Splitting", + "uri":"gaussdb_11_0017.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"33" + }, + { + "desc":"After read/write splitting is enabled, you can change the read/write splitting address.Changing the read/write splitting address will interrupt database connections and s", + "product_code":"gaussdb", + "title":"Changing the Read/Write Splitting Address", + "uri":"gaussdb_11_0031.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"34" + }, + { + "desc":"After read/write splitting is enabled, you can assign read weights as required.After read/write splitting is enabled, you can assign read weights for the primary node and", + "product_code":"gaussdb", + "title":"Assigning Read Weights", + "uri":"gaussdb_11_0018.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"35" + }, + { + "desc":"If load balancing is enabled for a database proxy instance, the security group associated with the proxy instance does not apply. You need to use access control to grant ", + "product_code":"gaussdb", + "title":"Enabling or Disabling Access Control", + "uri":"gaussdb_11_0025.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"36" + }, + { + "desc":"You can disable read/write splitting as required.If database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting address ", + "product_code":"gaussdb", + "title":"Disabling Read/Write Splitting", + "uri":"gaussdb_11_0019.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"37" + }, + { + "desc":"After read/write splitting is enabled, databases can be connected through a read/write splitting address. You can use internal SQL commands to verify the read/write split", + "product_code":"gaussdb", + "title":"Testing Read/Write Splitting Performance", + "uri":"gaussdb_11_0021.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"38" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"gaussdb", + "title":"Instance Modifications", + "uri":"gaussdb_03_0029.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"39" + }, { "desc":"You can change the name of a GaussDB(for MySQL) DB instance.The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lower", "product_code":"gaussdb", "title":"Changing a DB Instance Name", "uri":"gaussdb_03_0032.html", "doc_type":"usermanual", - "p_code":"31", - "code":"32" + "p_code":"39", + "code":"40" }, { - "desc":"You can change the CPU or memory (instance class) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "desc":"After an instance is created, you can add a description.Alternatively, click the instance name to go to the Basic Information page. In the DB Instance Information area, c", "product_code":"gaussdb", - "title":"Changing a DB Instance Class", + "title":"Changing an Instance Description", + "uri":"gaussdb_03_0132.html", + "doc_type":"usermanual", + "p_code":"39", + "code":"41" + }, + { + "desc":"You can change the vCPUs or memory of a DB instance as required. If the status of a DB instance changes from Changing instance specifications to Available, the change is ", + "product_code":"gaussdb", + "title":"Changing vCPUs and Memory of an Instance", "uri":"gaussdb_03_0092.html", "doc_type":"usermanual", - "p_code":"31", - "code":"33" + "p_code":"39", + "code":"42" }, { "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, you must reboot the DB instance for the modifications to take effec", @@ -302,8 +383,8 @@ "title":"Rebooting a DB Instance", "uri":"gaussdb_03_0040.html", "doc_type":"usermanual", - "p_code":"31", - "code":"34" + "p_code":"39", + "code":"43" }, { "desc":"You can export a DB instance list (containing all or selected DB instances) to view and analyze DB instance information.", @@ -311,8 +392,8 @@ "title":"Exporting DB Instance Information", "uri":"gaussdb_03_0045.html", "doc_type":"usermanual", - "p_code":"31", - "code":"35" + "p_code":"39", + "code":"44" }, { "desc":"You can manually delete a DB instance on the Instance Management page.If you delete a DB instance, the read replicas associated with it are also deleted.Deleted DB instan", @@ -320,8 +401,17 @@ "title":"Deleting a DB Instance", "uri":"gaussdb_03_0047.html", "doc_type":"usermanual", - "p_code":"31", - "code":"36" + "p_code":"39", + "code":"45" + }, + { + "desc":"GaussDB(for MySQL) supports manual minor version upgrades, which can improve performance, add new functions, and fix bugs.The upgrade will cause the instance to reboot an", + "product_code":"gaussdb", + "title":"Upgrading the Minor Version of a DB Instance", + "uri":"gaussdb_05_2265.html", + "doc_type":"usermanual", + "p_code":"39", + "code":"46" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -330,7 +420,7 @@ "uri":"gaussdb_03_0009.html", "doc_type":"usermanual", "p_code":"25", - "code":"37" + "code":"47" }, { "desc":"Currently, DB instances support read replicas.In read-intensive scenarios, a primary node may be unable to handle the read pressure and service performance may be affecte", @@ -338,8 +428,8 @@ "title":"Introducing Read Replicas", "uri":"gaussdb_03_0110.html", "doc_type":"usermanual", - "p_code":"37", - "code":"38" + "p_code":"47", + "code":"48" }, { "desc":"Read replicas are used to enhance the read capabilities and reduce read pressure on DB instances.After a DB instance is created, you can create read replicas for it.If yo", @@ -347,8 +437,8 @@ "title":"Creating a Read Replica", "uri":"gaussdb_03_0111.html", "doc_type":"usermanual", - "p_code":"37", - "code":"39" + "p_code":"47", + "code":"49" }, { "desc":"You can manage read replicas after they are created, such as promoting a read replica to the primary node and delete a read replica.", @@ -356,8 +446,8 @@ "title":"Managing a Read Replica", "uri":"gaussdb_03_0112.html", "doc_type":"usermanual", - "p_code":"37", - "code":"40" + "p_code":"47", + "code":"50" }, { "desc":"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 t", @@ -365,8 +455,8 @@ "title":"Promoting a Read Replica to the Primary Node", "uri":"gaussdb_03_0113.html", "doc_type":"usermanual", - "p_code":"37", - "code":"41" + "p_code":"47", + "code":"51" }, { "desc":"You can manually delete read replicas on the Instance Management page.Deleted read replicas cannot be restored. Exercise caution when performing this operation.You can de", @@ -374,8 +464,8 @@ "title":"Deleting a Read Replica", "uri":"gaussdb_03_0114.html", "doc_type":"usermanual", - "p_code":"37", - "code":"42" + "p_code":"47", + "code":"52" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -384,7 +474,7 @@ "uri":"gaussdb_03_0050.html", "doc_type":"usermanual", "p_code":"25", - "code":"43" + "code":"53" }, { "desc":"You can reset the administrator password of a DB instance.You can also reset the password of your database account when using GaussDB(for MySQL).You cannot reset the admi", @@ -392,8 +482,8 @@ "title":"Resetting the Administrator Password", "uri":"gaussdb_03_0051.html", "doc_type":"usermanual", - "p_code":"43", - "code":"44" + "p_code":"53", + "code":"54" }, { "desc":"You can change the security group of a DB instance.To submit the change, click .To cancel the change, click .", @@ -401,8 +491,8 @@ "title":"Changing a Security Group", "uri":"gaussdb_08_0003.html", "doc_type":"usermanual", - "p_code":"43", - "code":"45" + "p_code":"53", + "code":"55" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -411,7 +501,7 @@ "uri":"gaussdb_03_0055.html", "doc_type":"usermanual", "p_code":"25", - "code":"46" + "code":"56" }, { "desc":"GaussDB(for MySQL) supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window of your DB instances. GaussDB(", @@ -419,8 +509,8 @@ "title":"Working with Backups", "uri":"gaussdb_03_0056.html", "doc_type":"usermanual", - "p_code":"46", - "code":"47" + "p_code":"56", + "code":"57" }, { "desc":"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 inst", @@ -428,8 +518,8 @@ "title":"Creating a Manual Backup", "uri":"gaussdb_03_0058.html", "doc_type":"usermanual", - "p_code":"46", - "code":"48" + "p_code":"56", + "code":"58" }, { "desc":"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.The Create New Instance p", @@ -437,8 +527,8 @@ "title":"Restoring Data from a Backup", "uri":"gaussdb_03_0063.html", "doc_type":"usermanual", - "p_code":"46", - "code":"49" + "p_code":"56", + "code":"59" }, { "desc":"You can delete manual backups to release storage space.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups c", @@ -446,8 +536,8 @@ "title":"Deleting a Manual Backup", "uri":"gaussdb_03_0068.html", "doc_type":"usermanual", - "p_code":"46", - "code":"50" + "p_code":"56", + "code":"60" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -456,7 +546,7 @@ "uri":"gaussdb_08_0011.html", "doc_type":"usermanual", "p_code":"25", - "code":"51" + "code":"61" }, { "desc":"You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be", @@ -464,8 +554,8 @@ "title":"Creating a Parameter Template", "uri":"gaussdb_03_0072.html", "doc_type":"usermanual", - "p_code":"51", - "code":"52" + "p_code":"61", + "code":"62" }, { "desc":"You can modify parameters in a custom parameter template to optimize GaussDB(for MySQL) database performance.You can change parameter values in custom parameter templates", @@ -473,26 +563,26 @@ "title":"Modifying a Parameter Template", "uri":"gaussdb_08_0112.html", "doc_type":"usermanual", - "p_code":"51", - "code":"53" + "p_code":"61", + "code":"63" }, { "desc":"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 Te", "product_code":"gaussdb", - "title":"Exporting a Parameter Template", + "title":"Exporting Parameters", "uri":"gaussdb_08_0042.html", "doc_type":"usermanual", - "p_code":"51", - "code":"54" + "p_code":"61", + "code":"64" }, { - "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "desc":"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 defaul", "product_code":"gaussdb", "title":"Comparing a Parameter Template", "uri":"gaussdb_08_0012.html", "doc_type":"usermanual", - "p_code":"51", - "code":"55" + "p_code":"61", + "code":"65" }, { "desc":"You can view the change history of DB instance parameters or custom parameter templates.In a newly exported or created parameter template, the change history is blank.You", @@ -500,8 +590,8 @@ "title":"Viewing Parameter Change History", "uri":"gaussdb_05_0099.html", "doc_type":"usermanual", - "p_code":"51", - "code":"56" + "p_code":"61", + "code":"66" }, { "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", @@ -509,17 +599,17 @@ "title":"Replicating a Parameter Template", "uri":"gaussdb_08_0014.html", "doc_type":"usermanual", - "p_code":"51", - "code":"57" + "p_code":"61", + "code":"67" }, { - "desc":"You can reset all parameters in a custom parameter template to their default settings.After you reset a parameter template, click the DB instance to which the parameter t", + "desc":"You can reset all parameters in a custom parameter template to their default settings.", "product_code":"gaussdb", "title":"Resetting a Parameter Template", "uri":"gaussdb_08_0015.html", "doc_type":"usermanual", - "p_code":"51", - "code":"58" + "p_code":"61", + "code":"68" }, { "desc":"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_poo", @@ -527,8 +617,8 @@ "title":"Applying a Parameter Template", "uri":"gaussdb_05_0018.html", "doc_type":"usermanual", - "p_code":"51", - "code":"59" + "p_code":"61", + "code":"69" }, { "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance to which the parameter template applies, as well as the applic", @@ -536,8 +626,8 @@ "title":"Viewing Application Records of a Parameter Template", "uri":"gaussdb_05_0098.html", "doc_type":"usermanual", - "p_code":"51", - "code":"60" + "p_code":"61", + "code":"70" }, { "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.After you submit the modificatio", @@ -545,26 +635,26 @@ "title":"Modifying a Parameter Template Description", "uri":"gaussdb_08_0016.html", "doc_type":"usermanual", - "p_code":"51", - "code":"61" + "p_code":"61", + "code":"71" }, { - "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "desc":"You can delete a custom parameter template that is no longer needed.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", "product_code":"gaussdb", "title":"Deleting a Parameter Template", "uri":"gaussdb_08_0017.html", "doc_type":"usermanual", - "p_code":"51", - "code":"62" + "p_code":"61", + "code":"72" }, { - "desc":"GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:Consist of at least eight characters.Contain at least one uppercase let", + "desc":"GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:Consist of at least eight characters.Contain at least three types of th", "product_code":"gaussdb", "title":"Database Security", "uri":"gaussdb_03_0082.html", "doc_type":"usermanual", "p_code":"25", - "code":"63" + "code":"73" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -573,7 +663,7 @@ "uri":"gaussdb_03_0083.html", "doc_type":"usermanual", "p_code":"25", - "code":"64" + "code":"74" }, { "desc":"You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of monitoring metrics to be reporte", @@ -581,8 +671,8 @@ "title":"Configuring Displayed Metrics", "uri":"gaussdb_03_0085.html", "doc_type":"usermanual", - "p_code":"64", - "code":"65" + "p_code":"74", + "code":"75" }, { "desc":"You can set alarm rules for GaussDB(for MySQL) to customize the monitored objects and notification policies and stay aware of the GaussDB(for MySQL) operating status.The ", @@ -590,8 +680,8 @@ "title":"Setting Alarm Rules", "uri":"gaussdb_03_0087.html", "doc_type":"usermanual", - "p_code":"64", - "code":"66" + "p_code":"74", + "code":"76" }, { "desc":"The Cloud Eye service monitors operating statuses of DB instances. You can view the monitoring metrics of DB instances on the management console. By monitoring system res", @@ -599,8 +689,8 @@ "title":"Viewing Monitoring Metrics", "uri":"gaussdb_03_0088.html", "doc_type":"usermanual", - "p_code":"64", - "code":"67" + "p_code":"74", + "code":"77" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -609,7 +699,7 @@ "uri":"gaussdb_03_0013.html", "doc_type":"usermanual", "p_code":"25", - "code":"68" + "code":"78" }, { "desc":"Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for further querying, auditing, and backtracking. Table 1 lists the supported operations.", @@ -617,8 +707,8 @@ "title":"Key Operations Supported by CTS", "uri":"gaussdb_03_0014.html", "doc_type":"usermanual", - "p_code":"68", - "code":"69" + "p_code":"78", + "code":"79" }, { "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", @@ -626,8 +716,8 @@ "title":"Viewing Tracing Events", "uri":"gaussdb_03_0015.html", "doc_type":"usermanual", - "p_code":"68", - "code":"70" + "p_code":"78", + "code":"80" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -636,7 +726,7 @@ "uri":"gaussdb_03_0016.html", "doc_type":"usermanual", "p_code":"25", - "code":"71" + "code":"81" }, { "desc":"You can view database logs on the GaussDB console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.", @@ -644,8 +734,8 @@ "title":"Viewing Logs", "uri":"gaussdb_03_0017.html", "doc_type":"usermanual", - "p_code":"71", - "code":"72" + "p_code":"81", + "code":"82" }, { "desc":"GaussDB(for MySQL) log management allows you to view database-level logs, including error logs and slow SQL query logs.Error logs in different time periodsError logs of t", @@ -653,8 +743,8 @@ "title":"Viewing Error Logs", "uri":"gaussdb_03_0018.html", "doc_type":"usermanual", - "p_code":"71", - "code":"73" + "p_code":"81", + "code":"83" }, { "desc":"Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details and statistics to identify the statements that are executing", @@ -662,8 +752,44 @@ "title":"Viewing Slow Query Logs", "uri":"gaussdb_03_0019.html", "doc_type":"usermanual", - "p_code":"71", - "code":"74" + "p_code":"81", + "code":"84" + }, + { + "desc":"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", + "product_code":"gaussdb", + "title":"Enabling or Disabling SQL Explorer", + "uri":"gaussdb_03_0152.html", + "doc_type":"usermanual", + "p_code":"81", + "code":"85" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"gaussdb", + "title":"Task Center", + "uri":"gaussdb_05_0007.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"86" + }, + { + "desc":"You can view the progresses and results of tasks on the Task Center page.You can view and manage the following tasks:Creating a DB instanceRebooting a DB instanceDeleting", + "product_code":"gaussdb", + "title":"Viewing a Task", + "uri":"gaussdb_task_0001.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"87" + }, + { + "desc":"You can delete the task records no longer need to be displayed. The deletion only deletes the task records, and does not delete the DB instances or terminate the tasks th", + "product_code":"gaussdb", + "title":"Deleting a Task Record", + "uri":"gaussdb_task_0002.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"88" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -672,7 +798,7 @@ "uri":"gaussdb_faq.html", "doc_type":"usermanual", "p_code":"", - "code":"75" + "code":"89" }, { "desc":"GaussDB(for MySQL) supports the decoupling of compute and storage, improving your experience in terms of high availability, backup and restoration, upgrade and capacity e", @@ -680,8 +806,8 @@ "title":"Does GaussDB(for MySQL) Support Compute and Storage Decoupling?", "uri":"gaussdb_faq_0002.html", "doc_type":"usermanual", - "p_code":"75", - "code":"76" + "p_code":"89", + "code":"90" }, { "desc":"GaussDB(for MySQL) supports up to 128 TB of data and can easily handle large amounts of data requests.", @@ -689,8 +815,8 @@ "title":"What's the Maximum Data Volume Supported by GaussDB(for MySQL)?", "uri":"gaussdb_faq_0003.html", "doc_type":"usermanual", - "p_code":"75", - "code":"77" + "p_code":"89", + "code":"91" }, { "desc":"During the creation of a GaussDB(for MySQL) DB instance, a read replica is created by default in addition to a primary node. If the primary node fails, the system automat", @@ -698,8 +824,8 @@ "title":"Does GaussDB(for MySQL) Support Automatic Failover?", "uri":"gaussdb_faq_0005.html", "doc_type":"usermanual", - "p_code":"75", - "code":"78" + "p_code":"89", + "code":"92" }, { "desc":"If you modify the parameters in a parameter template, but the modifications do not take effect, you may need to reboot the DB instance associated with the parameter templ", @@ -707,8 +833,8 @@ "title":"What Should I Do When Modifications to GaussDB(for MySQL) Instance Parameters Does Not Take Effect?", "uri":"gaussdb_faq_0006.html", "doc_type":"usermanual", - "p_code":"75", - "code":"79" + "p_code":"89", + "code":"93" }, { "desc":"You can create a maximum of 15 read replicas for a GaussDB(for MySQL) DB instance.", @@ -716,8 +842,8 @@ "title":"How Many Read Replicas Can I Create for a GaussDB(for MySQL) DB Instance?", "uri":"gaussdb_faq_0007.html", "doc_type":"usermanual", - "p_code":"75", - "code":"80" + "p_code":"89", + "code":"94" }, { "desc":"MySQL provides client installation packages for different OSs on its official website. Click here to download the MySQL 8.0 client installation package or click here to d", @@ -725,8 +851,8 @@ "title":"How Can I Install the MySQL Client?", "uri":"gaussdb_faq_0011.html", "doc_type":"usermanual", - "p_code":"75", - "code":"81" + "p_code":"89", + "code":"95" }, { "desc":"Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.On the displayed console, choose File > Add/Remove Snap-in.In the left Available sn", @@ -734,8 +860,8 @@ "title":"How Can I Import the Root Certificate to a Windows or Linux OS?", "uri":"gaussdb_faq_0010.html", "doc_type":"usermanual", - "p_code":"75", - "code":"82" + "p_code":"89", + "code":"96" }, { "desc":"Perform the following steps to identify the problem:If they are in the same VPC, go to 2.If they are in different VPCs, create an ECS in the VPC where the DB instance is ", @@ -743,8 +869,8 @@ "title":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) DB Instance?", "uri":"gaussdb_faq_0009.html", "doc_type":"usermanual", - "p_code":"75", - "code":"83" + "p_code":"89", + "code":"97" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -753,6 +879,6 @@ "uri":"change_history.html", "doc_type":"usermanual", "p_code":"", - "code":"84" + "code":"98" } ] \ No newline at end of file diff --git a/docs/gaussdb_mysql/umn/change_history.html b/docs/gaussdb_mysql/umn/change_history.html index b6448d58..a3870e14 100644 --- a/docs/gaussdb_mysql/umn/change_history.html +++ b/docs/gaussdb_mysql/umn/change_history.html @@ -8,18 +8,43 @@ -

2022-10-30

+

2023-04-06

-

This is the third official release.

-

Optimized the content in Step 1: Create a DB Instance.

+

Added Changing an Instance Description.

+ + +

2022-11-30

+ +

Modified the following content:

+ + + +

2021-12-09

+ +

Modified the following content:

+ + + +

2021-11-30

+ +

Optimized Deleting a Task Record.

+ + +

2021-08-31

+ +

Added Enabling or Disabling SQL Explorer.

+ + +

2020-10-31

+ +

Optimized the content in Configuring Displayed Metrics.

2020-07-31

-

This is the second official release.

-

Modified the following content:

+

Modified the following content:

- +

2020-07-14

diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400783488.png b/docs/gaussdb_mysql/umn/en-us_image_0000001212611256.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400783488.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001212611256.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001352059444.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352059444.png new file mode 100644 index 00000000..4b1ef62e Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001352059444.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001401103264.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352219096.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001401103264.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352219096.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554244.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352219100.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0291554244.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352219100.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451343129.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352219136.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451343129.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352219136.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400623516.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352378996.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400623516.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352378996.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001401103272.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352379000.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001401103272.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352379000.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400943256.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352379004.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400943256.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352379004.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400783432.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352379036.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400783432.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352379036.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451103529.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352379040.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451103529.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352379040.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451103469.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352379048.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451103469.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352379048.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400783516.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352379056.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400783516.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352379056.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183173.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352538844.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183173.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352538844.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400623556.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352538852.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400623556.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352538852.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001401103224.png b/docs/gaussdb_mysql/umn/en-us_image_0000001352538904.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001401103224.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001352538904.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400271265.png b/docs/gaussdb_mysql/umn/en-us_image_0000001400271265.png new file mode 100644 index 00000000..973daaeb Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001400271265.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400391461.png b/docs/gaussdb_mysql/umn/en-us_image_0000001400391461.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001400391461.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183145.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402858817.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183145.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402858817.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001401103308.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402858853.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001401103308.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402858853.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183185.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402858861.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183185.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402858861.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451103533.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402858869.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451103533.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402858869.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183161.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402979141.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183161.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402979141.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400783456.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402979149.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400783456.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402979149.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451343169.png b/docs/gaussdb_mysql/umn/en-us_image_0000001402979157.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451343169.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001402979157.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451103505.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403138681.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451103505.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403138681.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400943340.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403138685.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400943340.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403138685.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451023297.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403138693.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451023297.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403138693.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183233.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403138721.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183233.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403138721.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183121.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403138737.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183121.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403138737.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451183189.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403218681.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451183189.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403218681.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001400943280.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403218685.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001400943280.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403218685.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001451023269.png b/docs/gaussdb_mysql/umn/en-us_image_0000001403218753.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0000001451023269.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001403218753.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001405262769.png b/docs/gaussdb_mysql/umn/en-us_image_0000001405262769.png new file mode 100644 index 00000000..f41f9130 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001405262769.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001405277053.png b/docs/gaussdb_mysql/umn/en-us_image_0000001405277053.png new file mode 100644 index 00000000..5c8bef8c Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001405277053.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001420606766.png b/docs/gaussdb_mysql/umn/en-us_image_0000001420606766.png new file mode 100644 index 00000000..bcf7a6b1 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001420606766.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001423775818.png b/docs/gaussdb_mysql/umn/en-us_image_0000001423775818.png new file mode 100644 index 00000000..5cc171e5 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001423775818.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001446730040.png b/docs/gaussdb_mysql/umn/en-us_image_0000001446730040.png new file mode 100644 index 00000000..adf11de3 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001446730040.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0192953998.png b/docs/gaussdb_mysql/umn/en-us_image_0000001472729081.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0192953998.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001472729081.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001480810240.png b/docs/gaussdb_mysql/umn/en-us_image_0000001480810240.png new file mode 100644 index 00000000..168c349d Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001480810240.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001496610421.png b/docs/gaussdb_mysql/umn/en-us_image_0000001496610421.png new file mode 100644 index 00000000..ad79b27d Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001496610421.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001496889725.png b/docs/gaussdb_mysql/umn/en-us_image_0000001496889725.png new file mode 100644 index 00000000..ceebf4a0 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001496889725.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001497009921.png b/docs/gaussdb_mysql/umn/en-us_image_0000001497009921.png new file mode 100644 index 00000000..ceebf4a0 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001497009921.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001497009925.png b/docs/gaussdb_mysql/umn/en-us_image_0000001497009925.png new file mode 100644 index 00000000..ad79b27d Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001497009925.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554272.png b/docs/gaussdb_mysql/umn/en-us_image_0000001512768946.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0291554272.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001512768946.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001513008494.png b/docs/gaussdb_mysql/umn/en-us_image_0000001513008494.png new file mode 100644 index 00000000..4b159e16 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001513008494.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001525318837.png b/docs/gaussdb_mysql/umn/en-us_image_0000001525318837.png new file mode 100644 index 00000000..c8d49ac8 Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001525318837.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554304.png b/docs/gaussdb_mysql/umn/en-us_image_0000001563528757.png similarity index 100% rename from docs/gaussdb_mysql/umn/en-us_image_0291554304.png rename to docs/gaussdb_mysql/umn/en-us_image_0000001563528757.png diff --git a/docs/gaussdb_mysql/umn/en-us_image_0000001563934877.png b/docs/gaussdb_mysql/umn/en-us_image_0000001563934877.png new file mode 100644 index 00000000..168c349d Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0000001563934877.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0218527002.png b/docs/gaussdb_mysql/umn/en-us_image_0218527002.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/gaussdb_mysql/umn/en-us_image_0218527002.png differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554155.png b/docs/gaussdb_mysql/umn/en-us_image_0291554155.png deleted file mode 100644 index 7dfb0f9e..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554155.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554160.png b/docs/gaussdb_mysql/umn/en-us_image_0291554160.png deleted file mode 100644 index e34868dc..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554160.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554168.png b/docs/gaussdb_mysql/umn/en-us_image_0291554168.png deleted file mode 100644 index 7cabd619..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554168.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554181.png b/docs/gaussdb_mysql/umn/en-us_image_0291554181.png deleted file mode 100644 index 6be9b671..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554181.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554184.png b/docs/gaussdb_mysql/umn/en-us_image_0291554184.png deleted file mode 100644 index 4ba2bdf4..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554184.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554204.png b/docs/gaussdb_mysql/umn/en-us_image_0291554204.png deleted file mode 100644 index bfec4154..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554204.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554226.png b/docs/gaussdb_mysql/umn/en-us_image_0291554226.png deleted file mode 100644 index 76f21bf5..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554226.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554230.png b/docs/gaussdb_mysql/umn/en-us_image_0291554230.png deleted file mode 100644 index 541a805a..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554230.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554259.png b/docs/gaussdb_mysql/umn/en-us_image_0291554259.png deleted file mode 100644 index 97358745..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554259.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554276.png b/docs/gaussdb_mysql/umn/en-us_image_0291554276.png deleted file mode 100644 index 97358745..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554276.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554292.png b/docs/gaussdb_mysql/umn/en-us_image_0291554292.png deleted file mode 100644 index e34868dc..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554292.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554294.png b/docs/gaussdb_mysql/umn/en-us_image_0291554294.png deleted file mode 100644 index c4ab9077..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554294.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554298.png b/docs/gaussdb_mysql/umn/en-us_image_0291554298.png deleted file mode 100644 index c4ab9077..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554298.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554315.png b/docs/gaussdb_mysql/umn/en-us_image_0291554315.png deleted file mode 100644 index 1267615e..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554315.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554316.png b/docs/gaussdb_mysql/umn/en-us_image_0291554316.png deleted file mode 100644 index dffd855a..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554316.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554324.png b/docs/gaussdb_mysql/umn/en-us_image_0291554324.png deleted file mode 100644 index 62ddb8e0..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554324.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554325.png b/docs/gaussdb_mysql/umn/en-us_image_0291554325.png deleted file mode 100644 index 4ba2bdf4..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554325.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554330.png b/docs/gaussdb_mysql/umn/en-us_image_0291554330.png deleted file mode 100644 index 70a7eda6..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554330.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554358.png b/docs/gaussdb_mysql/umn/en-us_image_0291554358.png deleted file mode 100644 index 63ff29aa..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554358.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554365.png b/docs/gaussdb_mysql/umn/en-us_image_0291554365.png deleted file mode 100644 index b26f87fc..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554365.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554383.png b/docs/gaussdb_mysql/umn/en-us_image_0291554383.png deleted file mode 100644 index 7dfb0f9e..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554383.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554386.png b/docs/gaussdb_mysql/umn/en-us_image_0291554386.png deleted file mode 100644 index 541a805a..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554386.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554390.png b/docs/gaussdb_mysql/umn/en-us_image_0291554390.png deleted file mode 100644 index 1267615e..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554390.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554391.png b/docs/gaussdb_mysql/umn/en-us_image_0291554391.png deleted file mode 100644 index 63ff29aa..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554391.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/en-us_image_0291554398.png b/docs/gaussdb_mysql/umn/en-us_image_0291554398.png deleted file mode 100644 index f261eb7e..00000000 Binary files a/docs/gaussdb_mysql/umn/en-us_image_0291554398.png and /dev/null differ diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0001.html b/docs/gaussdb_mysql/umn/gaussdb_01_0001.html index ea33ef16..fbac9923 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0001.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0001.html @@ -2,7 +2,7 @@

Basic Concepts

Understanding the following concepts helps you better use GaussDB(for MySQL):

-
diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0002.html b/docs/gaussdb_mysql/umn/gaussdb_01_0002.html index b3a797f2..cd80c219 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0002.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0002.html @@ -2,8 +2,8 @@

Product Benefits

GaussDB(for MySQL) is an enterprise-class cloud database that uses a decoupled compute and storage architecture.

-

Requirements and Pain Points

-
Table 1 Requirements and pain points

Requirements and Pain Points

+

Requirements

+
diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0003.html b/docs/gaussdb_mysql/umn/gaussdb_01_0003.html index 54b682b2..e0eedbdc 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0003.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0003.html @@ -4,7 +4,7 @@
    -
  • DB Instance Classes
    +
  • DB Instance Specifications
  • DB Engines and Versions
    • diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0004.html b/docs/gaussdb_mysql/umn/gaussdb_01_0004.html index 653251ab..8f056bb6 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0004.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0004.html @@ -1,31 +1,85 @@ -

    DB Instance Classes

    -

    GaussDB(for MySQL) instance classes are listed in the following table and vary according to actual situations.

    +

    DB Instance Specifications

    +

    GaussDB(for MySQL) instance specifications are listed in the following table and vary according to actual situations.

    -
Table 1 Requirements

Requirements

Description
Table 1 Instance classes

Instance Class

+
- - - - - - - - - + + + + + + + + +
Table 1 x86 instance specifications

Instance Specifications

vCPUs

+

vCPUs

Memory (GB)

+

Memory (GB)

General-enhanced

+

Dedicated Edition

16

+

4

64

+

32

32

+

8

128

+

64

60

+

16

256

+

128

+

32

+

256

+

64

+

512

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0006.html b/docs/gaussdb_mysql/umn/gaussdb_01_0006.html index 82fbc0dc..04532cad 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0006.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0006.html @@ -34,12 +34,17 @@ + + + - diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0008.html b/docs/gaussdb_mysql/umn/gaussdb_01_0008.html index d4d9d52f..8ffe657b 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0008.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0008.html @@ -20,7 +20,7 @@ - diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0004.html b/docs/gaussdb_mysql/umn/gaussdb_02_0004.html index dce634c6..535f8640 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

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click GaussDB.
  4. On the Instance Management page, click Create DB Instance.
  5. On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.

    +

    Procedure

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List. Under Database, click GaussDB.
    4. On the Instance Management page, click Create DB Instance.
    5. On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.

Table 2 Kunpeng instance specifications

Instance Specifications

+

vCPUs

+

Memory (GB)

+

Dedicated Edition

+

4

+

32

+

8

+

64

+

16

+

128

+

32

+

256

+

48

+

384

+

60

+

480

DB instance is being rebooted.

Changing a DB instance name

+

The instance name is being changed.

+

Changing port

DB instance port is being changed.

Changing instance class

+

Changing instance specifications

CPU or memory of a DB instance is being changed.

ECSs in which GaussDB(for MySQL) DB instances are deployed are not visible to users. You can access GaussDB(for MySQL) DB instances only over an IP address and a port.

Database root permissions

+

Administrator root permission

Only the root user permissions are available on the instance creation page.
Table 1 Basic information

Parameter

Description

@@ -47,19 +47,19 @@
-
Table 2 Specifications and storage

Parameter

+
- - - -
Table 2 Specifications and storage

Parameter

Description

+

Description

Instance Class

+

Instance Specifications

Refers to the CPU and memory of a DB instance. Different instance classes support different numbers of database connections and maximum IOPS.

-

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

+

Refers to the CPU and memory of a DB instance. Different instance specifications support different numbers of database connections and maximum IOPS.

+

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

Read Replicas

+

Nodes

GaussDB(for MySQL) supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time.

After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating a Read Replica.

@@ -74,9 +74,9 @@
-
Table 3 Network

Parameter

+
- @@ -89,7 +89,7 @@
Table 3 Network

Parameter

Description

+

Description

Subnet

Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets are only valid for a given AZ. The Dynamic Host Configuration Protocol (DHCP) function must be enabled by default for subnets in which you plan to create DB instances. It cannot be disabled. You can select or search for a desired subnet from the drop-down list.

-

A private IP address for write is automatically assigned when you are creating a DB instance. You can also enter an unused a private IP address for write in the subnet CIDR block.

+

A private IP address is automatically assigned when you create an instance. You can also enter a free private IP address in the subnet CIDR block.

Security Group

@@ -102,7 +102,7 @@
-
Table 4 Database configuration

Parameter

+
@@ -129,9 +129,9 @@
Table 4 Database configuration

Parameter

Description

-
Table 5 Parameter template

Parameter

+
- @@ -144,6 +144,21 @@
Table 5 Parameter template

Parameter

Description

+

Description
+ +
+ + + + + + + +
Table 6 Batch instance creation

Parameter

+

Description

+

Quantity

+

You can create instances in batches. The default value is 1. The value ranges from 1 to 10. If you create multiple instances at a time, a hyphen (-) followed by a number with four digits will be appended to the instance name, starting with -0001. For example, if you enter instance, the first instance will be named as instance-0001, the second as instance-0002, and so on.

+
+

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

    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0006.html b/docs/gaussdb_mysql/umn/gaussdb_02_0006.html index ae231c76..80e65607 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0006.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0006.html @@ -5,8 +5,8 @@

    If you are using GaussDB(for MySQL) for the first time, see Constraints.

    Process

    Figure 1 illustrates the process of connecting to a DB instance over a private network.

    -
    Figure 1 Connecting to a DB instance over a private network
    -
    • Step 1: Create a DB instance. Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.
    • Step 2: Configure security group rules.
      • If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance Over a Private Network.
      • If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
        • DB instance: Configure an inbound rule for the security group with which the DB instance is associated.
        • ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
        +
        Figure 1 Connecting to a DB instance over a private network
        +
        • Step 1: Create a DB instance. Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.
        • Step 2: Configure security group rules.
          • If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance Over a Private Network.
          • If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
            • DB instance: Configure an inbound rule for the security group to which the DB instance is associated.
            • ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security group rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
        • Step 3: Connect to a DB instance over a private network. You can connect to the DB instance through a common connection, or an SSL connection for enhanced security. SSL connections are encrypted.
    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html index 00569f68..a82057e7 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html @@ -3,7 +3,7 @@

    Step 2: Configure Security Group Rules

    Scenarios

    A security group is a collection of access control rules for ECSs and DB instances that have the same security requirements and are mutually trusted in a VPC. To ensure database security and reliability, you need to configure security group rules to allow specific IP addresses and ports to access DB instances.

    Check whether the ECS and DB instance are in the same security group.

    -
    • If they are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance Over a Private Network.
    • If they are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
      • DB instance: Configure an inbound rule for the security group with which the DB instance is associated.
      • ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
      +
      • If they are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance Over a Private Network.
      • If they are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
        • DB instance: Configure an inbound rule for the security group to which the DB instance is associated.
        • ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.

    Precautions

    The default security group rule allows all outgoing data packets. If an ECS and a DB instance are in the same security group, they can access each other. When a security group is created, you can configure security group rules to control access to and from DB instances in that security group.

    @@ -12,39 +12,55 @@

    If you use 0.0.0.0/0, all IP addresses are enabled to access DB instances in the security group.

    -

    Procedure

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List. Under Database, click GaussDB.
    4. On the Instance Management page, click the target DB instance.
    5. Configure security group rules.

      In the Network Information area on the Basic Information page, click the security group.

      +

      Procedure

      1. Log in to the management console.
      2. Click in the upper left corner and select a region and a project.
      3. Click Service List. Under Database, click GaussDB.
      4. On the Instance Management page, click the target DB instance.
      5. Configure security group rules.

        In the Network Information area on the Basic Information page, click the security group.

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

        +
        - - - - - - - - - - - + + + + + + + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0009.html b/docs/gaussdb_mysql/umn/gaussdb_02_0009.html index c0792569..31248691 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0009.html @@ -15,8 +15,8 @@ -

        Using MySQL-Front to Connect to a DB Instance

        1. Start MySQL-Front.
        2. In the displayed dialog box, click New.

          Figure 1 Connection management
          -

        3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

          Figure 2 Adding an account
          +

          Using MySQL-Front to Connect to a DB Instance

          1. Start MySQL-Front.
          2. In the displayed dialog box, click New.

            Figure 1 Connection management
            +

          3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

            Figure 2 Adding an account
        Table 1 Inbound rule parameter description

        Parameter

        Description

        +

        Description

        Example Value

        +

        Example Value

        Protocol

        +

        Protocol & Port

        +

        +

        Specifies the network protocol.

        +

        Network protocol for which the security group rule takes effect.

        +
        • Currently, the value can be All, TCP (All ports), TCP (Custom ports), UDP (All ports), UDP (Custom ports), ICMP, GRE, or others.
        • All: indicates all protocol ports are supported.

        TCP

        +

        TCP

        Port & Source

        +

        Port: Port or port range over which the traffic can reach your ECS.

        • Port: specifies the port or port range over which the traffic can reach your ECS. The value ranges from 1025 to 65534, excluding the followings which are occupied by the system and cannot be used: 5342, 5343, 5344, 5345, 12017, 20000, 20201, and 20202.
        • Source: specifies the source of the security group rule. The value can be another security group, a CIDR block, or an IP address.

          xxx.xxx.xxx.xxx/32 (IPv4 address)

          -

          xxx.xxx.xxx.0/24 (subnet)

          -

          0.0.0.0/0 (any IP address)

          -
        -
        • When connecting to the DB instance over a private network, enter the ECS's IP address and target DB instance's port.
        • When connecting to the DB instance over a public network, enter the local device's IP address and target DB instance's port.
        +

        When connecting to the instance through a private network, enter the port of the instance.

        +
        • Individual port: Enter a port, such as 22.
        • Consecutive ports: Enter a port range, such as 22-30.
        • All ports: Leave it blank or enter 1-65535.

        Description

        +

        Source

        Provides supplementary information about the security group rule. This parameter is optional.

        -

        The description can contain a maximum of 255 characters and cannot contain angle brackets (<>).

        +

        Source: specifies the source of the security group rule. The value can be another security group, a CIDR block, or an IP address.

        +

        xxx.xxx.xxx.xxx/32 (IPv4 address)

        +

        xxx.xxx.xxx.0/24 (subnet)

        +

        0.0.0.0/0 (any IP address)

        N/A

        +

        0.0.0.0/0

        +

        Description

        +

        Provides supplementary information about the security group rule. This parameter is optional.

        +

        The description can contain a maximum of 255 characters and cannot contain angle brackets (<>).

        +

        -

        +

        Operation

        +

        You can copy or delete a security group rule. If there is only one security group rule, the security group rule cannot be deleted.

        +

        -
        @@ -53,10 +53,10 @@
        Table 1 Parameter description

        Parameter
        -

      7. In the displayed window, select the connection that you have created and click Open. If the connection information is correct, the DB instance is successfully connected.

        Figure 3 Opening a session
        +

      8. In the displayed window, select the connection that you have created and click Open. If the connection information is correct, the DB instance is successfully connected.

        Figure 3 Opening a session

        9. -

        SSL Connection

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click GaussDB.
        4. In the DB Instance Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
        5. Import the root certificate to the Linux OS on the ECS.

          For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

          +

          SSL Connection

          1. Log in to the management console.
          2. Click in the upper left corner and select a region and a project.
          3. Click Service List. Under Database, click GaussDB.
          4. In the DB Instance Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
          5. Import the root certificate to the Linux OS on the ECS.

            For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

          6. Connect to a DB instance. The Linux OS is assumed in this example.

            mysql -h <hostName> -P <port> -u <userName> -p --ssl-ca=<caName>

            Table 2 Parameter description

            Parameter

            diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0011.html b/docs/gaussdb_mysql/umn/gaussdb_02_0011.html new file mode 100644 index 00000000..2e2083fb --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0011.html @@ -0,0 +1,20 @@ + + +

            Introducing Read/Write Splitting

            +

            Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read replicas are created by referring to Enabling Read/Write Splitting. Write requests are automatically routed to the primary node and read requests are routed to read replicas or the primary node by user-defined weights.

            +

            Constraints

            • Read/write splitting can be enabled only when at least one read replica is created.
            • After read/write splitting is enabled, the database port, private IP address, and security group cannot be changed.
            • Proxy does not support READ-UNCOMMITTED transaction isolation.
            • A maximum of four proxy instances can be created for a GaussDB(for MySQL) instance.
            • To use database proxy instances, ensure that the data in a single row of a table cannot exceed 16 MB.
            +
            • After read/write splitting is enabled, both the database port and the security group of the primary node and read replicas are changed.
            • Read/write splitting does not support SSL encryption.
            • Read/write splitting does not support the compression protocol.
            • If multi-statements are executed, all subsequent requests will be routed to the primary node. To restore the read/write splitting function, you need to disconnect the connection between applications and the read/write splitting address and establish a connection again.
            • The port number of the proxy instance is independent of that of the DB instance. Changing the port number of the DB instance does not change the port number of the proxy instance.
            +
            +

            Scenarios

            When enabling read/write splitting for an instance, you need to select the nodes (including the primary node and read replicas) to be associated to the proxy instances.

            +
            • 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.
            +
            • A primary node or read replica can be added to multiple proxy instances at the same time, and then is assigned different read weights. For details about how to assign weights, Assigning Read Weights.
            +
            • 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.
            +
            Figure 1 Multiple proxy instances
            +
            +
            + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0012.html b/docs/gaussdb_mysql/umn/gaussdb_02_0012.html index 541622ca..d0e8729e 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0012.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

            1. Log in to the management console.
            2. Click in the upper left corner and select a region and a project.
            3. Click Service List. Under Database, click GaussDB.
            4. On the Instance Management page, click Create DB Instance.
            5. On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.

              +

              Procedure

              1. Log in to the management console.
              2. Click in the upper left corner and select a region and a project.
              3. Click Service List. Under Database, click GaussDB.
              4. On the Instance Management page, click Create DB Instance.
              5. On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.

                Table 1 Basic information

                Parameter

                Description

                @@ -47,19 +47,19 @@
                -
                Table 2 Specifications and storage

                Parameter

                +
                - - - -
                Table 2 Specifications and storage

                Parameter

                Description

                +

                Description

                Instance Class

                +

                Instance Specifications

                Refers to the CPU and memory of a DB instance. Different instance classes support different numbers of database connections and maximum IOPS.

                -

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

                +

                Refers to the CPU and memory of a DB instance. Different instance specifications support different numbers of database connections and maximum IOPS.

                +

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

                Read Replicas

                +

                Nodes

                GaussDB(for MySQL) supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time.

                After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating a Read Replica.

                @@ -74,9 +74,9 @@
                -
                Table 3 Network

                Parameter

                +
                - @@ -89,7 +89,7 @@
                Table 3 Network

                Parameter

                Description

                +

                Description

                Subnet

                Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets are only valid for a given AZ. The Dynamic Host Configuration Protocol (DHCP) function must be enabled by default for subnets in which you plan to create DB instances. It cannot be disabled. You can select or search for a desired subnet from the drop-down list.

                -

                A private IP address for write is automatically assigned when you are creating a DB instance. You can also enter an unused a private IP address for write in the subnet CIDR block.

                +

                A private IP address is automatically assigned when you create an instance. You can also enter a free private IP address in the subnet CIDR block.

                Security Group

                @@ -102,7 +102,7 @@
                -
                Table 4 Database configuration

                Parameter

                +
                @@ -129,9 +129,9 @@
                Table 4 Database configuration

                Parameter

                Description

                -
                Table 5 Parameter template

                Parameter

                +
                - @@ -144,6 +144,21 @@
                Table 5 Parameter template

                Parameter

                Description

                +

                Description
                + +
                + + + + + + + +
                Table 6 Batch instance creation

                Parameter

                +

                Description

                +

                Quantity

                +

                You can create instances in batches. The default value is 1. The value ranges from 1 to 10. If you create multiple instances at a time, a hyphen (-) followed by a number with four digits will be appended to the instance name, starting with -0001. For example, if you enter instance, the first instance will be named as instance-0001, the second as instance-0002, and so on.

                +
                +

              6. Confirm your specifications.

                • If you need to modify your settings, click Previous.
                • If you do not need to modify your settings, click Submit.

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

                diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0013.html b/docs/gaussdb_mysql/umn/gaussdb_02_0013.html index 5eb27bbb..d80a7e8c 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0013.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0013.html @@ -11,7 +11,7 @@

                If you use 0.0.0.0/0, all IP addresses are enabled to access DB instances in the security group.

                -

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select a region and a project.
                3. Click Service List. Under Database, click GaussDB.
                4. On the Instance Management page, click the target DB instance.
                5. Configure security group rules.

                  In the Network Information area on the Basic Information page, click the security group.

                  +

                  Procedure

                  1. Log in to the management console.
                  2. Click in the upper left corner and select a region and a project.
                  3. Click Service List. Under Database, click GaussDB.
                  4. On the Instance Management page, click the target DB instance.
                  5. Configure security group rules.

                    In the Network Information area on the Basic Information page, click the security group.

                  6. 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.
                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0014.html b/docs/gaussdb_mysql/umn/gaussdb_02_0014.html index d6136f1c..9960948d 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0014.html @@ -13,8 +13,8 @@ -

                    Using MySQL-Front to Connect to a DB Instance

                    1. Start MySQL-Front.
                    2. In the displayed dialog box, click New.

                      Figure 1 Connection management
                      -

                    3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

                      Figure 2 Adding an account
                      +

                      Using MySQL-Front to Connect to a DB Instance

                      1. Start MySQL-Front.
                      2. In the displayed dialog box, click New.

                        Figure 1 Connection management
                        +

                      3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

                        Figure 2 Adding an account
                    Table 1 Inbound rule parameter description

                    Parameter
                    @@ -29,7 +29,7 @@ -
                    Table 1 Parameter description

                    Parameter

                    Host

                    EIP bound the target DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address for Write field in the Network Information area.

                    +

                    EIP bound to the target DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address (EIP) field in the Network Information area.

                    Port

                    @@ -50,13 +50,13 @@
                    -

                  7. In the displayed window, select the connection that you have created in Figure 3 and click Open.

                    If the connection information is correct, the DB instance is successfully connected.
                    Figure 3 Opening a session
                    +

                  8. In the displayed window, select the connection that you have created in Figure 3 and click Open.

                    If the connection information is correct, the DB instance is successfully connected.
                    Figure 3 Opening a session

                    If the connection fails, ensure that preparations have been correctly made in Prerequisites and try again.

                  -

                  Using SSL to Connect to a DB Instance

                  1. Log in to the management console.
                  2. Click in the upper left corner and select a region and a project.
                  3. Click Service List. Under Database, click GaussDB.
                  4. In the DB Instance Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
                  5. Import the root certificate to the Linux OS on the ECS.

                    For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

                    +

                    Using SSL to Connect to a DB Instance

                    1. Log in to the management console.
                    2. Click in the upper left corner and select a region and a project.
                    3. Click Service List. Under Database, click GaussDB.
                    4. In the DB Instance Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
                    5. Import the root certificate to the Linux OS on the ECS.

                      For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

                    6. Connect to a DB instance. The Linux OS is assumed in this example.

                      mysql -h <hostName> -P <port> -u <userName> -p --ssl-ca=<caName>
                      @@ -66,7 +66,7 @@ -
                      Table 2 Parameter description

                      Parameter

                      <hostName>

                      Host IP address of the target DB instance to be connected. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address for Write field in the Network Information area.

                      +

                      Host IP address of the target DB instance to be connected. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address (EIP) field in the Network Information area.

                      <port>

                      diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html index 0c37516c..870b2fcf 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html @@ -5,7 +5,7 @@

                      Precautions

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

                      Procedure

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click GaussDB.
                      4. On the Instance Management page, click the target DB instance.
                      5. In the Network Information area, click Bind in the Private IP Address for Write field.
                      6. 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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, click the target DB instance.
                        5. In the Network Information area, click Bind in the Private IP Address field.
                        6. 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.

                        7. On the EIPs page, view the EIP that has been bound to the DB instance.
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0016.html b/docs/gaussdb_mysql/umn/gaussdb_02_0016.html index eef76edc..51cc849c 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0016.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0016.html @@ -5,7 +5,7 @@

                        If you are using GaussDB(for MySQL) for the first time, see Constraints.

                        Process

                        Figure 1 illustrates the process of connecting to a DB instance over a public network.

                        -
                        Figure 1 Connecting to a DB instance over a public network
                        +
                        Figure 1 Connecting to a DB instance over a public network
                        • Step 1: Create a DB instance. Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.
                        • Step 2: Bind an EIP. The Elastic IP service provides independent public IP addresses and bandwidth for public access. You can apply for an EIP on the VPC console and bind the EIP to the DB instance.
                        • Step 3: Configure security group rules. To access a DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the DB instance.
                        • Step 4: Connect to a DB instance over a public network. You can connect to a DB instance through a common connection, or an SSL connection for enhanced security. SSL connections are encrypted.
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0007.html b/docs/gaussdb_mysql/umn/gaussdb_03_0007.html index dc3c6a19..cf9fa984 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0007.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0007.html @@ -1,12 +1,12 @@

                        Migrating Data to GaussDB(for MySQL) Using mysqldump

                        -

                        Preparing for Data Migration

                        GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through an ECS or EIP.

                        +

                        Preparing for Data Migration

                        GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through a private network or EIP.

                        1. Prepare an ECS in the same VPC subnet as GaussDB(for MySQL) or prepare a device for accessing GaussDB(for MySQL) over a public network.
                          • To connect to a DB instance through an ECS, you must first create an ECS.

                            For details on how to create and log in to an ECS, see descriptions about creating an ECS and logging in an ECS in the Elastic Cloud Server User Guide.

                          • To connect to a DB instance through an EIP, you must:
                            1. Bind the EIP to the DB instance. For details, see Binding an EIP.
                            2. Ensure that the local device can access the EIP that has been bound to the DB instance.
                        2. Install the MySQL client on the prepared ECS or device.

                          For details, see How Can I Install the MySQL Client?

                          -

                          The MySQL client version must be the same as that installed on the GaussDB(for MySQL) DB instance. The MySQL database or client provides the mysqldump and mysql tools by default.

                          +

                          The version of the GaussDB(for MySQL) client must be the same as or later than that of the GaussDB(for MySQL) server. The MySQL database or client provides the mysqldump and mysql tools by default.

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

                        Enter the database password as prompted.

                        Example:

                        mysqldump --databases gaussdb --single-transaction --hex-blob --set-gtid-purged=OFF --no-create-info --skip-triggers -u root -p -h 192.168.151.18 -P 3306 -r dump-data.sql

                        -

                        After this command is executed, the dump-data.sql file will be generated.

                        +

                        After this command is executed, the dump-data.sql file will be generated.

                      Importing Data

                      You can use a client to connect to a GaussDB(for MySQL) DB instance through an ECS or a device and then import the exported SQL file into that DB instance.

                      diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0010.html b/docs/gaussdb_mysql/umn/gaussdb_03_0010.html index 5674f45f..f87d4a09 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0010.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0010.html @@ -1,6 +1,6 @@ -

                      Database Connections

                      +

                      Connection Management

                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0011.html b/docs/gaussdb_mysql/umn/gaussdb_03_0011.html index 98da9a81..6fc5d764 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0011.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0011.html @@ -7,18 +7,18 @@

                      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

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click GaussDB.
                      4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                      5. In the Network Information area, click Bind in the Public IP Address for Write field.
                      6. 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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                        5. In the Network Information area, click Bind in the Public IP Address (EIP) field.
                        6. 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.

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

                        -

                        Unbinding an EIP

                        1. On the Instance Management page, click the DB instance that has been bound with an EIP. The Basic Information page is displayed.
                        2. In the Network Information area, click Unbind in the Public IP Address for Write field.
                        3. In the displayed dialog box, click Yes.
                        4. To bind an EIP to the DB instance again, see Binding an EIP.
                        +

                        Unbinding an EIP

                        1. On the Instance Management page, click the DB instance that has been bound with an EIP. The Basic Information page is displayed.
                        2. In the Network Information area, click Unbind in the Public IP Address (EIP) field.
                        3. In the displayed dialog box, click Yes.
                        4. To bind an EIP to the DB instance again, see Binding an EIP.
                        -
                        Parent topic: Database Connections
                        +
                        Parent topic: Connection Management
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html index 30ef9f60..8d3fb0d0 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html @@ -1,18 +1,20 @@

                        Changing a Database Port

                        -

                        Scenarios

                        You can change the database port of a GaussDB(for MySQL) DB instance. The change applies to the ports of the primary node and read replicas, and may affect services intermittently.

                        +

                        Scenarios

                        You can change the database port of a GaussDB(for MySQL) instance. The change applies to the ports of the primary node and read replicas, and may affect services intermittently.

                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                        5. 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.
                              1. 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.
                              2. This process takes about 1–5 minutes.
                              +

                              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

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click GaussDB.
                              4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                              5. 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.
                                    1. 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.
                                    2. This process takes about 1–5 minutes.
                                  -
                                • To cancel the change, click .
                                +
                              6. To cancel the change, click .

                        6. View the result of the change on the Basic Information page.
                        -
                        Parent topic: Database Connections
                        +
                        Parent topic: Connection Management
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0015.html b/docs/gaussdb_mysql/umn/gaussdb_03_0015.html index 1c80784b..826b5edc 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0015.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0015.html @@ -4,9 +4,9 @@

                        Scenarios

                        After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.

                        This section describes how to query the operation records of last 7 days on the CTS console.

                        -

                        Procedure

                        1. Log in to the management console.
                        2. Choose Management & Governance > Cloud Trace Service.
                        3. Choose Trace List in the navigation pane on the left.
                        4. Filter conditions to query traces. The details are described as follows:

                          • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

                            When you select Resource ID for Search By, you also need to select or enter a resource ID.

                            +

                            Procedure

                            1. Log in to the management console.
                            2. Choose Management & Deployment > Cloud Trace Service.
                            3. Choose Trace List in the navigation pane on the left.
                            4. Filter conditions to query traces. The details are described as follows:

                              • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

                                When you select Resource ID for Search By, you also need to select or enter a resource ID.

                              • Operator: Select a specific operator from the drop-down list.
                              • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
                              • In the upper right corner of the page, you can specify a time range for querying traces.
                              -

                            5. Select the search criteria, and click Query.
                            6. Click on the left of the required trace to expand its details.
                            7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                            8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                              For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                              +

                            9. Select the search criteria, and click Query.
                            10. Click on the left of the required trace to expand its details.
                            11. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                            12. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                              For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0016.html b/docs/gaussdb_mysql/umn/gaussdb_03_0016.html index d31e2eac..1cd53097 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0016.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0016.html @@ -10,6 +10,8 @@
                      7. Viewing Slow Query Logs
                        8. +
                      8. Enabling or Disabling SQL Explorer
                        +
                        9. diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0018.html b/docs/gaussdb_mysql/umn/gaussdb_03_0018.html index f908b2df..7b0c5a22 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0018.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0018.html @@ -2,7 +2,7 @@

                        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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                        5. In the navigation pane on the left, choose Logs.
                        6. 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
                            +

                            Viewing Log Details

                            1. Log in to the management console.
                            2. Click in the upper left corner and select a region and a project.
                            3. Click Service List. Under Database, click GaussDB.
                            4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                            5. In the navigation pane on the left, choose Logs.
                            6. 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 7a79efa9..a98bf961 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html @@ -5,7 +5,7 @@
                            GaussDB(for MySQL) supports the following statement types:
                            • SELECT
                            • INSERT
                            • UPDATE
                            • DELETE
                            • CREATE
                            • ALTER
                            • DROP
                        -

                        Viewing Log Details

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                        5. In the navigation pane on the left, choose Logs.
                        6. 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

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click GaussDB.
                          4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                          5. In the navigation pane on the left, choose Logs.
                          6. 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.

                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0029.html b/docs/gaussdb_mysql/umn/gaussdb_03_0029.html index 5ec0ddea..1f58672d 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0029.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0029.html @@ -1,12 +1,14 @@ -

                        DB Instance Management

                        +

                        Instance Modifications

                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html index 1567e1a3..67715151 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html @@ -3,14 +3,14 @@

                        Changing a DB Instance Name

                        Scenarios

                        You can change the name of a GaussDB(for MySQL) DB instance.

                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. 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.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click GaussDB.
                          4. 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.

                          5. View the result of the change on the Basic Information page.
                        -
                        Parent topic: DB Instance Management
                        +
                        Parent topic: Instance Modifications
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0040.html b/docs/gaussdb_mysql/umn/gaussdb_03_0040.html index 36fce09b..28b131fd 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0040.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0040.html @@ -1,19 +1,19 @@

                        Rebooting a DB Instance

                        -

                        Scenarios

                        You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, you must reboot the DB instance for the modifications to take effect. DB instances can be rebooted only when they are in the available state. They cannot be rebooted when backups or read replicas are being created for them.

                        +

                        Scenarios

                        You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, you must reboot the DB instance for the modifications to take effect. Instances cannot be rebooted when backups or read replicas are being created for them.

                        The time required for rebooting a DB instance depends on the crash recovery process of the DB engine. To shorten the reboot time, you are advised to reduce database activities during the reboot to reduce rollback activities of transit transactions.

                        -
                        • You can reboot a DB instance only when its status is Available. Your database may be unavailable in some cases such as data is being backed up or some modifications are 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.
                        +
                        • 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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, locate the target DB instance and choose More > Reboot in the Operation column.

                          Alternatively, click the target DB instance. On the displayed page, click Reboot in the upper right corner of the page.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click GaussDB.
                          4. On the Instance Management page, locate the target DB instance and choose More > Reboot 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.

                          5. In the displayed Reboot DB Instance dialog box, click Yes.
                          6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
                        -
                        Parent topic: DB Instance Management
                        +
                        Parent topic: Instance Modifications
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0045.html b/docs/gaussdb_mysql/umn/gaussdb_03_0045.html index 9bbd3c27..235c222b 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0045.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0045.html @@ -3,14 +3,14 @@

                        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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. 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.
                        5. After the export task is complete, a .csv file is generated locally.
                        +

                        Exporting Information About All DB Instances

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. 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.
                        5. After the export task is complete, a .csv file is generated locally.
                        -

                        Exporting Information About Selected DB Instances

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. 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.
                        5. After the export task is complete, a .csv file is generated locally.
                        +

                        Exporting Information About Selected DB Instances

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. 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.
                        5. After the export task is complete, a .csv file is generated locally.
                        -
                        Parent topic: DB Instance Management
                        +
                        Parent topic: Instance Modifications
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0047.html b/docs/gaussdb_mysql/umn/gaussdb_03_0047.html index 967b00ee..3d009142 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0047.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0047.html @@ -7,12 +7,12 @@

                        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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, locate the DB instance to be deleted and click More > Delete in the Operation column.
                        5. In the displayed dialog box, click Yes. Refresh the Instance Management page later to check that the deletion is successful.
                        +

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, locate the DB instance to be deleted and click More > Delete in the Operation column.
                        5. In the displayed dialog box, click Yes. Refresh the Instance Management page later to check that the deletion is successful.
                        -
                        Parent topic: DB Instance Management
                        +
                        Parent topic: Instance Modifications
                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html index 027b402b..d303b86e 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html @@ -8,13 +8,13 @@
                        • 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

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click GaussDB.
                        4. On the Instance Management page, locate the target DB instance and choose More > Reset Password in the Operation column.
                        5. Enter a new password and confirm the password.

                          Keep this password secure. The system cannot retrieve it.

                          +

                          Method 1

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click GaussDB.
                          4. On the Instance Management page, locate the target DB instance and choose More > Reset Password in the Operation column.
                          5. 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

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click GaussDB.
                          4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                          5. 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

                            1. Log in to the management console.
                            2. Click in the upper left corner and select a region and a project.
                            3. Click Service List. Under Database, click GaussDB.
                            4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                            5. 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.
                              • To submit the new password, click OK.
                              • To cancel the reset, click Cancel.
                              diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html index 1b4013e0..ab358d03 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html @@ -1,16 +1,14 @@

                              Creating a Manual Backup

                              -

                              Scenarios

                              GaussDB(for MySQL) allows you to create manual backups for available primary nodes. You can restore data from backups to ensure data reliability.

                              +

                              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

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click GaussDB.
                              4. On the Instance Management page, locate the target DB instance and choose More > Create Backup in the Operation column.
                              5. 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.
                                -

                              6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                -

                              +

                              Method 1

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click GaussDB.
                              4. On the Instance Management page, locate the target DB instance and choose More > Create Backup in the Operation column.
                              5. 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.
                                +

                              6. After a manual backup has been created, you can view and manage it on the Backup Management page.
                              -

                              Method 2

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click GaussDB.
                              4. On the Instance Management page, click the target DB instance.
                              5. 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.
                                -

                              6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                -

                              +

                              Method 2

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click GaussDB.
                              4. On the Instance Management page, click the target DB instance.
                              5. 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.
                                +

                              6. After a manual backup has been created, you can view and manage it on the Backup Management page.
                              diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0063.html b/docs/gaussdb_mysql/umn/gaussdb_03_0063.html index 00a8d537..17f45e40 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

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click GaussDB.
                              4. On the Backup Management page, select the backup to be restored and click Restore in the Operation column.
                              5. Click OK. Currently, you can only restore data to a new DB instance.

                                The Create New Instance page is displayed.

                                +

                                Procedure

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click GaussDB.
                                4. On the Backup Management page, select the backup to be restored and click Restore in the Operation column.
                                5. 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.

                                6. 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 fc3a2ecd..5ac7f13f 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

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click GaussDB.
                                4. 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:

                                  +

                                  Procedure

                                  1. Log in to the management console.
                                  2. Click in the upper left corner and select a region and a project.
                                  3. Click Service List. Under Database, click GaussDB.
                                  4. 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:

                                    • Automated backups
                                    • Backups that are being restored

                                  5. Click Yes.
                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0072.html b/docs/gaussdb_mysql/umn/gaussdb_03_0072.html index 14ea1ad2..823dd6f1 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

                                  1. Log in to the management console.
                                  2. Click in the upper left corner and select a region and a project.
                                  3. Click Service List. Under Database, click GaussDB.
                                  4. On the Parameter Template Management page, click Create Parameter Template.
                                  5. 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

                                    1. Log in to the management console.
                                    2. Click in the upper left corner and select a region and a project.
                                    3. Click Service List. Under Database, click GaussDB.
                                    4. On the Parameter Template Management page, click Create Parameter Template.
                                    5. 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_0082.html b/docs/gaussdb_mysql/umn/gaussdb_03_0082.html index a3fe6bf0..7959b942 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0082.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0082.html @@ -3,7 +3,7 @@

                                  Database Security

                                  Password Strength Requirements

                                  -
                                  GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:
                                  • Consist of at least eight characters.
                                  • Contain at least one uppercase letter, one lowercase letter, one digit, and one special character.
                                  +
                                  GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:
                                  • Consist of at least eight characters.
                                  • Contain at least three types of the following: uppercase letters, lowercase letters, digits, and special characters.

                                  When you create DB instances, your password strength is checked. You can modify the password strength as user root. For security reasons, you are advised to use a password that is at least as strong as the default one.

                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0087.html b/docs/gaussdb_mysql/umn/gaussdb_03_0087.html index a0f2781e..e602d4f7 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0087.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0087.html @@ -4,7 +4,7 @@

                                  Scenarios

                                  You can set alarm rules for GaussDB(for MySQL) to customize the monitored objects and notification policies and stay aware of the GaussDB(for MySQL) operating status.

                                  The GaussDB(for MySQL) alarm rules include alarm rule names, services, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

                                  -

                                  Procedure

                                  1. Log in to the management console.
                                  2. Under Management & Deployment, click Cloud Eye.
                                  3. In the navigation pane on the left, choose Cloud Service Monitoring > GaussDB(for MySQL).
                                  4. Locate the DB instance for which you want to create an alarm rule and click on the left, and then click Create Alarm Rule in the Operation column.
                                  5. On the displayed page, set parameters as required.

                                    • Specify Name and Description.
                                    • Select Use template for Method. The template contains the following common metrics: CPU usage, memory usage, and storage space usage.
                                    • Click to enable alarm notification. The validity period is 24 hours by default. If the topics you require are not displayed in the drop-down list, click Create an SMN topic. Then, select Generated alarm and Cleared alarm for Trigger Condition.

                                      Cloud Eye sends notifications only within the validity period specified in the alarm rule.

                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      2. Under Management & Deployment, click Cloud Eye.
                                      3. In the navigation pane on the left, choose Cloud Service Monitoring > GaussDB(for MySQL).
                                      4. Locate the DB instance for which you want to create an alarm rule and click on the left, and then click Create Alarm Rule in the Operation column.
                                      5. On the displayed page, set parameters as required.

                                        • Specify Name and Description.
                                        • Select Use template for Method. The template contains the following common metrics: CPU usage, memory usage, and storage space usage.
                                        • Click to enable alarm notification. The validity period is 24 hours by default. If the topics you require are not displayed in the drop-down list, click Create an SMN topic. Then, select Generated alarm and Cleared alarm for Trigger Condition.

                                          Cloud Eye sends notifications only within the validity period specified in the alarm rule.

                                      6. Click Create. The alarm rule is created.

                                        For operation details, see the Cloud Eye User Guide.

                                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html index b90f468a..07762050 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html @@ -12,7 +12,7 @@
                                        • The DB instance keeps running properly for about 10 minutes.

                                          For a newly created DB instance, you need to wait for a while before viewing the monitoring metrics.

                                      -

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click GaussDB.
                                      4. 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

                                        1. Log in to the management console.
                                        2. Click in the upper left corner and select a region and a project.
                                        3. Click Service List. Under Database, click GaussDB.
                                        4. 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:

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

                                        5. 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 a70b1b14..bc29922b 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0092.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0092.html @@ -1,24 +1,22 @@ -

                                        Changing a DB Instance Class

                                        -

                                        Scenarios

                                        You can change the CPU or memory (instance class) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

                                        -
                                        • A DB instance cannot be deleted while its instance class is being changed.
                                        • The instance class can be changed only at the DB instance level. The instance class of the primary node or read replicas cannot be changed separately for a GaussDB(for MySQL) DB instance.
                                        -
                                        • Changing the DB instance class will cause the instance to reboot. To prevent service interruptions, change the instance class during off-peak hours.
                                        • To prevent traffic congestion during peak hours, you are advised to reboot the DB instance during off-peak hours.
                                        +

                                        Changing vCPUs and Memory of an Instance

                                        +

                                        Scenarios

                                        You can change the vCPUs or memory of a DB instance as required. If the status of a DB instance changes from Changing instance specifications to Available, the change is successful.

                                        +
                                        • An instance cannot be deleted when its specifications are being changed.
                                        • The vCPUs and memory can be changed only at the instance level. The specifications of the primary node or read replicas cannot be changed separately for a given instance.
                                        +
                                        • 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

                                        1. Log in to the management console.
                                        2. Click in the upper left corner and select a region and a project.
                                        3. Click Service List. Under Database, click GaussDB.
                                        4. You can change the instance class in either of the following ways:

                                          • On the Instance Management page, locate the target DB instance and choose More > Change Instance Class 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 Class field.
                                          -

                                        5. On the displayed page, specify the new instance class and scheduled time, and click Next.

                                          Choose either of the following scheduled time:

                                          -
                                          • Upon submission: The instance class will be changed upon the task submission.
                                          • In maintenance window: The instance class will be changed in your specified maintenance window.
                                          -

                                        6. On the displayed page, confirm the instance class.

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

                                        7. View the DB instance class change result.

                                          Changing the instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instance Management page is Changing instance class. After a few minutes, click the instance and view the instance class on the displayed Basic Information page to check that the change is successful.

                                          -

                                          After the DB instance class is 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.

                                          +

                                          Procedure

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click GaussDB.
                                          4. 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.
                                            +

                                          5. On the displayed page, specify the new instance specifications, and click Next.
                                          6. 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.
                                            +

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

                                            +

                                            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.

                                          -
                                          Parent topic: DB Instance Management
                                          +
                                          Parent topic: Instance Modifications
                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0110.html b/docs/gaussdb_mysql/umn/gaussdb_03_0110.html index 7d320257..b3014b6f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0110.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0110.html @@ -7,7 +7,7 @@

                                          Functions

                                          • Specifications of read replicas are the same as those of the primary node.
                                          • You do not need to maintain accounts and databases for read replicas. They are synchronized from the primary node.
                                          • Read replicas support system performance monitoring.

                                            GaussDB(for MySQL) provides nearly 20 monitoring metrics, including the CPU usage, memory usage, storage space usage, and database connections. You can view these metrics to understand the load of DB instances.

                                          -

                                          Constraints

                                          • A DB instance contains up to 15 read replicas.
                                          • Read replicas do not support backup settings or temporary backups.
                                          • Read replicas do not support instance creation at any time point or restoration from backup files to the original instance to overwrite data.
                                          • Data cannot be migrated to read replicas.
                                          • Read replicas do not support database creation and deletion.
                                          • Read replicas do not support account creation. You can create accounts only on the primary node.
                                          +

                                          Constraints

                                          • A DB instance contains up to 15 read replicas.
                                          • Read replicas do not support backup settings or temporary backups.
                                          • Read replicas do not support instance creation at any point of time or restoration from backup files to the original instance to overwrite data.
                                          • Data cannot be migrated to read replicas.
                                          • Read replicas do not support database creation and deletion.
                                          • Read replicas do not support account creation. You can create accounts only on the primary node.
                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0111.html b/docs/gaussdb_mysql/umn/gaussdb_03_0111.html index 45610754..a68b4e1d 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

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click GaussDB.
                                          4. 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 topology on the Basic Information page, click to create read replicas.

                                            +

                                            Procedure

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select a region and a project.
                                            3. Click Service List. Under Database, click GaussDB.
                                            4. 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.

                                            5. On the displayed page, specify Failover Priority and Quantity and then click Create Now.
                                            6. 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 64dea3cd..198d8eec 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

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click GaussDB.
                                          4. Click the target DB instance to go to the Basic Information page.
                                          5. At the bottom of the Basic Information page, you can view and manage all read replicas associated with the DB instance.
                                          +

                                          Procedure

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click GaussDB.
                                          4. Click the target DB instance to go to the Basic Information page.
                                          5. 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 92b52de6..2adbc88f 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

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click GaussDB.
                                          4. On the Instance Management page, click the target DB instance.
                                          5. At the bottom of the Basic Information page, locate the read replica to be promoted and click Promote to Primary in the Operation column.
                                          6. 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

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click GaussDB.
                                              4. On the Instance Management page, click the target DB instance.
                                              5. At the bottom of the Basic Information page, locate the read replica to be promoted and click Promote to Primary in the Operation column.
                                              6. 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.

                                              @@ -11,7 +11,7 @@

                                              Each read replica has a failover priority that determines the order in which it is promoted when recovering from a primary node failure.

                                              • Priorities range from 1 for the first priority to 16 for the last priority.
                                              • If two or more read replicas share the same priority, they have a same probability of being promoted to the new primary node.

                                              GaussDB(for MySQL) selects a read replica and promotes it to the new primary node as follows:

                                              -
                                              1. Find all read replicas that are available for a promotion.
                                              2. Fine one or more read replicas with the highest priority.
                                              3. Promote an arbitrary read replica with the highest priority. If the promotion fails due to network faults or abnormal replication status, GaussDB(for MySQL) attempts to promote another read replica by priority until the promotion is successful.
                                              +
                                              1. Find all read replicas that are available for a promotion.
                                              2. Find one or more read replicas with the highest priority.
                                              3. If the promotion fails due to network faults or abnormal replication status, GaussDB(for MySQL) attempts to promote another read replica by priority until the promotion is successful.
                                              diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0114.html b/docs/gaussdb_mysql/umn/gaussdb_03_0114.html index e18d375f..e20b3701 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

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click GaussDB.
                                              4. On the Instance Management page, click the target DB instance.
                                              5. 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

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click GaussDB.
                                                4. On the Instance Management page, click the target DB instance.
                                                5. 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.

                                                6. In the displayed dialog box, click Yes. Refresh the Instance Management 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 new file mode 100644 index 00000000..c7b8b97b --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0132.html @@ -0,0 +1,19 @@ + + +

                                              Changing an Instance Description

                                              +

                                              Scenarios

                                              After an instance is created, you can add a description.

                                              +
                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click in the upper left corner of the page and choose Databases > GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                              4. 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 .
                                                +

                                              5. View the results on the Basic Information page.

                                                Alternatively, view the results on the Instances page.

                                                +

                                              +
                                              +
                                              +
                                              +
                                              +
                                              Parent topic: Instance Modifications
                                              +
                                              +
                                              + diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0152.html b/docs/gaussdb_mysql/umn/gaussdb_03_0152.html new file mode 100644 index 00000000..84e69784 --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0152.html @@ -0,0 +1,19 @@ + + +

                                              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

                                              1. Log in to the console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                              4. On the Instances page, click the instance name to go to the Basic Information page.
                                              5. In the navigation pane on the left, choose Advanced O&M.
                                              6. 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
                                                +

                                                SQL data is stored for 1 day by default and will be automatically deleted after that time expires.

                                                +
                                                +

                                              +
                                              +

                                              Disabling SQL Explorer

                                              1. Log in to the console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                              4. On the Instances page, click the instance name to go to the Basic Information page.
                                              5. In the navigation pane on the left, choose Advanced O&M. Click SQL Explorer and set to .
                                              +
                                              +
                                              +
                                              +
                                              +
                                              Parent topic: Logs
                                              +
                                              +
                                              + diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0007.html b/docs/gaussdb_mysql/umn/gaussdb_05_0007.html new file mode 100644 index 00000000..ff21b533 --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_05_0007.html @@ -0,0 +1,17 @@ + + +

                                              Task Center

                                              +
                                              + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0018.html b/docs/gaussdb_mysql/umn/gaussdb_05_0018.html index e1183d92..16cde251 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

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click GaussDB.
                                              4. 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

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click GaussDB.
                                                4. 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.

                                                  A parameter template can be applied to one or more DB instances.

                                                5. 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 3c8e2083..6ce29058 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

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click GaussDB.
                                                4. After a parameter template applies to a DB instance successfully, 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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. 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.

                                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0099.html b/docs/gaussdb_mysql/umn/gaussdb_05_0099.html index db9639ee..1b3751cb 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

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click GaussDB.
                                                4. On the Instance Management page, click the target DB instance.
                                                5. 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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. On the Instance Management page, click the target DB instance.
                                                  5. 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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                  5. 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

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                    5. 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.

                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_2265.html b/docs/gaussdb_mysql/umn/gaussdb_05_2265.html new file mode 100644 index 00000000..63aec8fc --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_05_2265.html @@ -0,0 +1,17 @@ + + +

                                                  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.

                                                  +
                                                  +

                                                  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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click in the upper left corner of the page and choose Database > GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                                  4. On the Instances page, click the instance name to go to the Basic Information page.
                                                  5. In the DB Instance Information area, click Upgrade in the DB Engine Version field.
                                                  6. 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.

                                                    +

                                                  +
                                                  +
                                                  +
                                                  +
                                                  +
                                                  Parent topic: Instance Modifications
                                                  +
                                                  +
                                                  + diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0003.html b/docs/gaussdb_mysql/umn/gaussdb_08_0003.html index 05e6b9e5..f3988c8f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0003.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0003.html @@ -3,8 +3,8 @@

                                                  Changing a Security Group

                                                  Scenarios

                                                  You can change the security group of a DB instance.

                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                                  5. In the Network Information area, click in the Security Group field.

                                                    • To submit the change, click .
                                                    • To cancel the change, click .
                                                    -

                                                  6. 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.
                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                                  5. In the Network Information area, click in the Security Group field.

                                                    • To submit the change, click .
                                                    • To cancel the change, click .
                                                    +

                                                  6. 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.
                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0011.html b/docs/gaussdb_mysql/umn/gaussdb_08_0011.html index 33aa5e7b..b797f032 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0011.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0011.html @@ -8,7 +8,7 @@
                                                6. Modifying a Parameter Template
                                                  7. -
                                                7. Exporting a Parameter Template
                                                  +
                                                8. Exporting Parameters
                                                9. Comparing a Parameter Template
                                                  10. diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0012.html b/docs/gaussdb_mysql/umn/gaussdb_08_0012.html index 47a07aa4..e5359622 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0012.html @@ -1,13 +1,13 @@

                                                  Comparing a Parameter Template

                                                  -

                                                  Scenarios

                                                  You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

                                                  -

                                                  You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

                                                  +

                                                  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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. On the Instance Management page, click the target DB instance.
                                                  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Compare above the parameter list.
                                                  6. 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

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Instance Management page, click the target DB instance.
                                                    5. In the navigation pane on the left, choose Parameters. On the displayed page, click Compare above the parameter list.
                                                    6. 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

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                    5. 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

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click GaussDB.
                                                      4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                      5. 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.

                                                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0014.html b/docs/gaussdb_mysql/umn/gaussdb_08_0014.html index 1b977bbe..d00473f6 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0014.html @@ -5,7 +5,7 @@

                                                    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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click GaussDB.
                                                  4. 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

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. 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.

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

                                                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0015.html b/docs/gaussdb_mysql/umn/gaussdb_08_0015.html index 3eb4a539..48465e9c 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0015.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0015.html @@ -3,11 +3,7 @@

                                                    Resetting a Parameter Template

                                                    Scenarios

                                                    You can reset all parameters in a custom parameter template to their default settings.

                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                    5. Click Yes.

                                                      -

                                                      -

                                                      After you reset a parameter template, click the DB instance to which the parameter template is applied to view the status of the parameter template. On the displayed Basic Information page, if the status of the parameter template is Pending reboot, you must reboot the DB instance for the reset to take effect.

                                                      -
                                                      -

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                    5. Click Yes.
                                                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0016.html b/docs/gaussdb_mysql/umn/gaussdb_08_0016.html index e34c95b7..c7ed6bba 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.

                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Parameter Template Management page, click Custom Templates. Locate the parameter template you want to modify and click in the Description column.
                                                    5. 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

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click GaussDB.
                                                      4. On the Parameter Template Management page, click Custom Templates. Locate the parameter template you want to modify and click in the Description column.
                                                      5. 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: >!<"&'=

                                                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0017.html b/docs/gaussdb_mysql/umn/gaussdb_08_0017.html index e7f7291b..10d6dca8 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0017.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0017.html @@ -1,11 +1,11 @@

                                                    Deleting a Parameter Template

                                                    -

                                                    Scenarios

                                                    You can delete a custom parameter template that is no longer in use.

                                                    +

                                                    Scenarios

                                                    You can delete a custom parameter template that is no longer needed.

                                                    • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
                                                    • Default parameter templates cannot be deleted.
                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Parameter Template Management page, click Custom Templates. Locate the parameter template to be deleted and choose More > Delete in the Operation column.
                                                    5. In the displayed dialog box, click Yes.
                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Parameter Template Management page, click Custom Templates. Locate the parameter template to be deleted and choose More > Delete in the Operation column.
                                                    5. 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 ad942fa3..51084af9 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0042.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0042.html @@ -1,16 +1,11 @@ -

                                                    Exporting a Parameter Template

                                                    +

                                                    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

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. On the Instance Management page, click the target DB instance.
                                                    5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                      • Exporting to a custom template
                                                        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 carriage returns or the following special characters: >!<"&'=
                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click GaussDB.
                                                        4. On the Instance Management page, click the target DB instance.
                                                        5. 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 (_).

                                                          -
                                                        -

                                                        After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

                                                        -
                                                      • Exporting to a file
                                                        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.

                                                        The file name must start with a letter and consist of 4 to 64 characters. 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 15e419ef..2770c30b 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0112.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0112.html @@ -5,25 +5,24 @@

                                                    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

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click GaussDB.
                                                    4. In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates page, click the parameter template you want to view.
                                                    5. Modify parameters as required.

                                                      Available operations are as follows:

                                                      +

                                                      Modifying Parameter Template Parameters

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click GaussDB.
                                                      4. In the navigation pane on the left, choose Parameter Template Management. On the Custom Templates page, click the parameter template you want to view.
                                                      5. 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.
                                                        -

                                                      6. After the parameters are modified, you can click Change History to view the modification details.

                                                        The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.

                                                        +

                                                      7. After the parameters have been modified, you can click Change History to view the modification details.

                                                        The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.

                                                        • After modifying some parameters of a DB instance, you need to reboot the DB instance for the modifications to take effect.
                                                        • After modifying some parameters of a read replica, you need to reboot the read replica for the modifications to take effect.

                                                      -

                                                      Modifying Instance Parameters

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click GaussDB.
                                                      4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                                      5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

                                                        Available operations are as follows:

                                                        -

                                                        After you modify instance parameters, the modifications immediately take effect for the DB instance.

                                                        -

                                                        +

                                                        Modifying Instance Parameters

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click GaussDB.
                                                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                                        5. 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 Instance Management page is Pending reboot, you must reboot the DB instance for the modifications to take effect.
                                                          • If the value is No, the modifications take effect immediately.
                                                          +
                                                          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.
                                                          -
                                                          • 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.

                                                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html new file mode 100644 index 00000000..2d56558f --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html @@ -0,0 +1,19 @@ + + +

                                                        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

                                                        1. Log in to the console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                                        5. In the navigation pane on the left, choose Database Proxy.

                                                          Figure 1 Enabling read/write splitting
                                                          +

                                                        6. Click Create Proxy Instance.
                                                        7. 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.
                                                              +
                                                            +
                                                            +
                                                          • Proxy instance specifications: 2 vCPUs | 4 GB (general-enhanced), 4 vCPUs | 8 GB (general-enhanced), and 8 vCPUs | 16 GB (general-enhanced).
                                                          • Proxy Instance Nodes: The default value is 2. Enter an integer from 2 to 32. Number of recommended proxy instance nodes = (Number of vCPUs of the primary node + Total number of vCPUs of all read replicas)/(4 x Number of vCPUs of the proxy instance), rounded up.
                                                          +
                                                          • Read Weight: For instances with read/write splitting enabled, you can add or delete nodes and assign weights for the primary node and read replicas. Requests are assigned to the nodes based on the read weights you specify. For example, read weights assigned to one primary node and two read replicas are 100, 200, and 200, respectively. In the read/write mode, the primary node and two read replicas process read requests in the ratio of 1:2:2. The primary node processes 20% of read requests, and each read replica processes 40% of read requests. Write requests are automatically routed to the primary node. In the read-only mode, the read weight of the primary node does not take effect, and the two read replicas process 50% of read requests, respectively. For details, see Assigning Read Weights.
                                                          +

                                                        +
                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0018.html b/docs/gaussdb_mysql/umn/gaussdb_11_0018.html new file mode 100644 index 00000000..9b3b17e9 --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0018.html @@ -0,0 +1,28 @@ + + +

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

                                                        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:

                                                        +
                                                        • If the number of CPUs is 8, the weight is 400 (8 x 50 = 400).
                                                        • If the number of CPUs is 16, the weight is 800 (16 x 50 = 800).
                                                        • If the number of vCPUs is 32, the weight is 1000 (32 x 50 = 1600, rounded down to the maximum value within the range).
                                                        +
                                                        +
                                                        +
                                                        +

                                                        Procedure

                                                        1. Log in to the console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                                        4. On the Instance Management page, click the instance name to go to the Basic Information page.
                                                        5. In the navigation pane on the left, choose Database Proxy. On the displayed page, click the Read/Write Splitting tab.
                                                        6. 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 instances
                                                          +
                                                          • When there are multiple proxy instances, newly created read replicas are automatically associated with proxy instances and their read weights are 0 by default.
                                                          • If you want to associate a read replica with a proxy instance, go to the Basic Information page, locate the read replica in the Node List area, and click Associate with proxy instance. On the displayed page, select a proxy instance and click Assign Weight.
                                                          • After a read replica is deleted, its weight is automatically removed while the weights of other read replicas remain unchanged.
                                                          +
                                                          +
                                                          +

                                                        +
                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0019.html b/docs/gaussdb_mysql/umn/gaussdb_11_0019.html new file mode 100644 index 00000000..9fc0fbdc --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0019.html @@ -0,0 +1,15 @@ + + +

                                                        Disabling Read/Write Splitting

                                                        +

                                                        You can disable read/write splitting as required.

                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click GaussDB.
                                                        4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                                        5. In the navigation pane on the left, choose Database Proxy.
                                                        6. 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.

                                                          +
                                                          +

                                                        +
                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0021.html b/docs/gaussdb_mysql/umn/gaussdb_11_0021.html new file mode 100644 index 00000000..5511e651 --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0021.html @@ -0,0 +1,15 @@ + + +

                                                        Testing Read/Write Splitting Performance

                                                        +

                                                        After read/write splitting is enabled, databases can be connected through a read/write splitting address. You can use internal SQL commands to verify the read/write splitting performance.

                                                        +

                                                        Procedure

                                                        1. Use a read/write splitting address to connect to the database. For details, see Enabling Read/Write Splitting.
                                                        2. Run the following command to view the routing result of the previous SQL statement. The result is the private IP address of the DB instance.

                                                          show last route;
                                                          +
                                                          Figure 1 Query result
                                                          +

                                                        +
                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0025.html b/docs/gaussdb_mysql/umn/gaussdb_11_0025.html new file mode 100644 index 00000000..7452d48f --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0025.html @@ -0,0 +1,19 @@ + + +

                                                        Enabling or Disabling Access Control

                                                        +

                                                        If load balancing is enabled for a database proxy instance, the security group associated with the proxy instance does not apply. You need to use access control to grant access from specific IP addresses.

                                                        +

                                                        Enabling Access Control

                                                        1. Log in to the console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                                        4. On the Instances page, click the instance name to go to the Basic Information page.
                                                        5. On the Database Proxy page, enable access control.

                                                          Locate the target proxy instance and click next to the Access Control area.

                                                          +

                                                        6. Click Configure. In the displayed dialog box, configure the access control mode and IP addresses or CIDR blocks.

                                                          • Access Control: The blacklist and whitelist cannot be configured at the same time. If you switch between lists, your previously entered settings will be lost. IP addresses or CIDR blocks in the blacklist are not allowed to access proxy instances.
                                                          • IP Address or CIDR Block: Enter valid IP addresses or CIDR blocks that meet the following requirements:
                                                            • Each line contains an IP address or a CIDR block and ends with a line break.
                                                            • Each IP address or CIDR block can include a description separated by a vertical bar symbol (|), for example, 192.168.10.10|GaussDB01. The description can include up to 50 characters but cannot contain angle brackets (<>).
                                                            • Up to 300 IP addresses or CIDR blocks can be added.
                                                            +
                                                          +

                                                        +
                                                        +

                                                        Disabling Access Control

                                                        1. Log in to the console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                                        4. On the Instances page, click the instance name to go to the Basic Information page.
                                                        5. On the Database Proxy page, disable access control.

                                                          Locate the target proxy instance and click next to the Access Control area.

                                                          +

                                                        +
                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0031.html b/docs/gaussdb_mysql/umn/gaussdb_11_0031.html new file mode 100644 index 00000000..01b7bd0b --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0031.html @@ -0,0 +1,21 @@ + + +

                                                        Changing the Read/Write Splitting Address

                                                        +

                                                        Scenarios

                                                        After read/write splitting is enabled, you can change the read/write splitting address.

                                                        +
                                                        +

                                                        Precautions

                                                        Changing the read/write splitting address will interrupt database connections and services. Therefore, change the read/write splitting address during off-peak hours or when services are stopped.

                                                        +
                                                        +

                                                        Constraints

                                                        The new IP address is not in use and must be in the same subnet as the GaussDB(for MySQL) instance.

                                                        +
                                                        +

                                                        Procedure

                                                        You can change the read/write splitting address for instances with read/write splitting enabled.

                                                        +
                                                        +
                                                        1. Log in to the console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Under Database, click GaussDB. In the navigation pane on the left, click GaussDB(for MySQL).
                                                        4. On the Instances page, click the instance name to go to the Basic Information page.
                                                        5. In the navigation pane on the left, click Database Proxy.

                                                          Click the desired proxy instance name. In the DB Instance Information area, click Change next to the Read/Write Splitting Address field.

                                                          +

                                                        6. In the displayed dialog box, enter a new IP address and click OK.

                                                          In-use IP addresses cannot be used.

                                                          +

                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0050.html b/docs/gaussdb_mysql/umn/gaussdb_11_0050.html new file mode 100644 index 00000000..5df8a47b --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0050.html @@ -0,0 +1,28 @@ + + +

                                                        Database Proxy (Read/Write Splitting)

                                                        +

                                                        +
                                                        + + diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0011.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0011.html index b548b638..dcfd59dc 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0011.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0011.html @@ -3,7 +3,7 @@

                                                        How Can I Install the MySQL Client?

                                                        MySQL provides client installation packages for different OSs on its official website. Click here to download the MySQL 8.0 client installation package or click here to download the packages of other versions. The following uses Red Hat Linux as an example to show how to obtain the required installation package and install it.

                                                        Procedure

                                                        1. Obtain the installation package.

                                                          Find the link to the required version on the download page. The mysql-community-client-8.0.21-1.el6.x86_64 is used as an example in the following.

                                                          -
                                                          Figure 1 Download
                                                          +
                                                          Figure 1 Download

                                                          Click No thanks, just start my download. to download the installation package.

                                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_task_0001.html b/docs/gaussdb_mysql/umn/gaussdb_task_0001.html new file mode 100644 index 00000000..d423b244 --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_task_0001.html @@ -0,0 +1,19 @@ + + +

                                                          Viewing a Task

                                                          +

                                                          You can view the progresses and results of tasks on the Task Center page.

                                                          +

                                                          You can view and manage the following tasks:

                                                          +
                                                          • Creating a DB instance
                                                          • Rebooting a DB instance
                                                          • Deleting a DB Instance
                                                          • Binding an EIP to a DB Instance
                                                          • Unbinding an EIP from a DB instance
                                                          • Changing instance specifications
                                                          • Promoting a read replica to the new primary node
                                                          • Changing a database port
                                                          • Changing a security group
                                                          • Creating a read replica
                                                          • Deleting a read replica
                                                          • Restoring data to a new DB instance
                                                          +
                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click GaussDB.
                                                          4. In the navigation pane on the left, choose Task Center. Locate the task and view its details.

                                                            • To identify the task, you can use the task name/ID or instance name/ID. Alternatively, click the drop-down list of All task types in the upper right corner and enter or select the task name.
                                                            • You can click in the right corner to view the progress and status of tasks in a specific period. The default period is seven days.

                                                              The task list can only show up to 30 days of past tasks.

                                                              +
                                                            • You can view tasks with the following statuses:
                                                              • Running
                                                              • Completed
                                                              • Failed
                                                              +
                                                            +

                                                          +
                                                          +
                                                          +
                                                          +
                                                          +
                                                          Parent topic: Task Center
                                                          +
                                                          +
                                                          + diff --git a/docs/gaussdb_mysql/umn/gaussdb_task_0002.html b/docs/gaussdb_mysql/umn/gaussdb_task_0002.html new file mode 100644 index 00000000..e2a1da01 --- /dev/null +++ b/docs/gaussdb_mysql/umn/gaussdb_task_0002.html @@ -0,0 +1,17 @@ + + +

                                                          Deleting a Task Record

                                                          +

                                                          You can delete the task records no longer need to be displayed. The deletion only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

                                                          +

                                                          Deleted task records cannot be recovered. Exercise caution when performing this operation.

                                                          +
                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click GaussDB.
                                                          4. Choose Task Center in the navigation pane on the left. On the displayed page, locate the task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                            You can delete instant task records in the following statuses:

                                                            +
                                                            • Running
                                                            • Completed
                                                            • Failed
                                                            +

                                                          +
                                                          +
                                                          +
                                                          +
                                                          +
                                                          Parent topic: Task Center
                                                          +
                                                          +
                                                          + diff --git a/docs/gaussdb_mysql/umn/gaussdb_usermanual.html b/docs/gaussdb_mysql/umn/gaussdb_usermanual.html index ec790913..f18bf307 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_usermanual.html +++ b/docs/gaussdb_mysql/umn/gaussdb_usermanual.html @@ -6,9 +6,11 @@
                                                        diff --git a/docs/gaussdb_mysql/umn/introduction.html b/docs/gaussdb_mysql/umn/introduction.html index 1b472040..f61ead2e 100644 --- a/docs/gaussdb_mysql/umn/introduction.html +++ b/docs/gaussdb_mysql/umn/introduction.html @@ -1,7 +1,7 @@

                                                        What Is GaussDB(for MySQL)?

                                                        -

                                                        GaussDB(for MySQL) is the latest generation enterprise-class distributed database. It is fully compatible with MySQL and provides high scalability and massive storage capacity. It uses a decoupled compute and storage architecture and supports up to 128 TB of storage. With GaussDB(for MySQL), there is no need to deal with sharding, and no need to worry about data loss. It combines the performance and availability of commercial databases with the cost-effectiveness of open source databases.

                                                        +

                                                        GaussDB(for MySQL) is the latest generation enterprise-class distributed database. It is fully compatible with MySQL and provides high scalability and massive storage capacity. It uses a decoupled compute and storage architecture and supports up to 128 TB of storage. With GaussDB(for MySQL), there is no need to deal with sharding, and no need to worry about data loss. It combines the performance and availability of commercial databases with the cost-effectiveness of open source databases.

                                                        A GaussDB(for MySQL) DB instance consists of one primary node (write node) and multiple read replicas (read-only nodes). They share the underlying DFV storage.

                                                        DB Engines and Versions lists the versions supported by GaussDB(for MySQL).