From 14126161938aedb8b716e02189c11c5331582fdb Mon Sep 17 00:00:00 2001 From: "Ru, Li Yi" Date: Tue, 11 Feb 2025 13:01:24 +0000 Subject: [PATCH] gaussdbformysql_umn_20250122 Reviewed-by: Wagner, Fabian Co-authored-by: Ru, Li Yi Co-committed-by: Ru, Li Yi --- docs/gaussdb_mysql/umn/ALL_META.TXT.json | 102 +++++++++--------- docs/gaussdb_mysql/umn/CLASS.TXT.json | 60 +++++------ docs/gaussdb_mysql/umn/change_history.html | 7 +- docs/gaussdb_mysql/umn/gaussdb_01_0001.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_01_0002.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_01_0004.html | 10 +- docs/gaussdb_mysql/umn/gaussdb_01_0005.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_01_0008.html | 22 ++-- docs/gaussdb_mysql/umn/gaussdb_01_0009.html | 10 +- docs/gaussdb_mysql/umn/gaussdb_02_0000.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_02_0004.html | 28 ++--- docs/gaussdb_mysql/umn/gaussdb_02_0005.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_02_0006.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_02_0008.html | 8 +- docs/gaussdb_mysql/umn/gaussdb_02_0009.html | 14 +-- docs/gaussdb_mysql/umn/gaussdb_02_0010.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_02_0012.html | 28 ++--- docs/gaussdb_mysql/umn/gaussdb_02_0013.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_02_0014.html | 16 +-- docs/gaussdb_mysql/umn/gaussdb_02_0015.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_02_0016.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_03_0007.html | 26 ++--- docs/gaussdb_mysql/umn/gaussdb_03_0009.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0011.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0012.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0014.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0017.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0019.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0032.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0047.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0051.html | 8 +- docs/gaussdb_mysql/umn/gaussdb_03_0056.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0058.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0069.html | 8 +- docs/gaussdb_mysql/umn/gaussdb_03_0082.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_03_0085.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_03_0087.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_03_0088.html | 14 +-- docs/gaussdb_mysql/umn/gaussdb_03_0092.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0110.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0111.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_03_0113.html | 12 +-- docs/gaussdb_mysql/umn/gaussdb_03_0114.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_05_0098.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_05_0100.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_05_2265.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_08_0112.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_11_0017.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_faq.html | 8 +- docs/gaussdb_mysql/umn/gaussdb_faq_0002.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_faq_0003.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_faq_0005.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_faq_0006.html | 2 +- docs/gaussdb_mysql/umn/gaussdb_faq_0007.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_faq_0009.html | 4 +- docs/gaussdb_mysql/umn/gaussdb_faq_0010.html | 6 +- docs/gaussdb_mysql/umn/gaussdb_task_0002.html | 2 +- .../gaussdb_mysql/umn/gaussdb_usermanual.html | 2 +- .../umn/gaussdbformysql_03_0131.html | 2 +- .../umn/gaussdbformysql_03_0133.html | 6 +- docs/gaussdb_mysql/umn/introduction.html | 4 +- docs/gaussdb_mysql/umn/quick_start.html | 12 +-- 62 files changed, 285 insertions(+), 280 deletions(-) diff --git a/docs/gaussdb_mysql/umn/ALL_META.TXT.json b/docs/gaussdb_mysql/umn/ALL_META.TXT.json index 11914aecc..96567455e 100644 --- a/docs/gaussdb_mysql/umn/ALL_META.TXT.json +++ b/docs/gaussdb_mysql/umn/ALL_META.TXT.json @@ -27,7 +27,7 @@ "code":"2", "des":"GaussDB(for MySQL) is the latest generation enterprise-class distributed database. It is fully compatible with MySQL and provides high scalability and massive storage cap", "doc_type":"usermanual", - "kw":"GaussDB(for MySQL),GaussDB(for MySQL),What Is GaussDB(for MySQL)?,Introduction,User Guide", + "kw":"What Is GaussDB(for MySQL)?,Introduction,User Guide", "search_title":"", "metedata":[ { @@ -61,7 +61,7 @@ "node_id":"gaussdb_01_0002.xml", "product_code":"gaussdb", "code":"4", - "des":"GaussDB(for MySQL) is an enterprise-class cloud database that uses a decoupled compute and storage architecture.Mass storage with 128 TB capacity and no sharding required", + "des":"GaussDB(for MySQL) is an enterprise-grade cloud database with decoupled compute and storage.Mass storage with 128 TB capacity and no sharding requiredEasy-to-use, fully c", "doc_type":"usermanual", "kw":"Product Benefits,Introduction,User Guide", "search_title":"", @@ -97,7 +97,7 @@ "node_id":"gaussdb_01_0004.xml", "product_code":"gaussdb", "code":"6", - "des":"GaussDB(for MySQL) instance specifications are listed in the following table and vary according to actual situations.", + "des":"GaussDB(for MySQL) instance specifications are listed in the following tables and vary according to actual situations.", "doc_type":"usermanual", "kw":"DB Instance Specifications,DB Instance Description,User Guide", "search_title":"", @@ -207,7 +207,7 @@ "code":"12", "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":"Getting Started with GaussDB(for MySQL)", + "kw":"Getting Started", "search_title":"", "metedata":[ { @@ -215,7 +215,7 @@ "documenttype":"usermanual" } ], - "title":"Getting Started with GaussDB(for MySQL)", + "title":"Getting Started", "githuburl":"" }, { @@ -223,9 +223,9 @@ "node_id":"quick_start.xml", "product_code":"gaussdb", "code":"13", - "des":"You can connect a DB instance over a private or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ECS is in the sam", + "des":"You can connect a DB instance over a private or public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ECS is in the same ", "doc_type":"usermanual", - "kw":"Connecting to a DB Instance,Getting Started with GaussDB(for MySQL),User Guide", + "kw":"Connecting to a DB Instance,Getting Started,User Guide", "search_title":"", "metedata":[ { @@ -243,7 +243,7 @@ "code":"14", "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":"Connecting to a DB instance Over a Private Network", + "kw":"Connecting to a DB Instance over a Private Network", "search_title":"", "metedata":[ { @@ -251,7 +251,7 @@ "documenttype":"usermanual" } ], - "title":"Connecting to a DB instance Over a Private Network", + "title":"Connecting to a DB Instance over a Private Network", "githuburl":"" }, { @@ -261,7 +261,7 @@ "code":"15", "des":"This section describes how to create a DB instance on the management console and then connect to that instance through an ECS over a private network.If you are using Gaus", "doc_type":"usermanual", - "kw":"SSL connections,are encrypted,Overview,Connecting to a DB instance Over a Private Network,User Guide", + "kw":"SSL connections,are encrypted,Overview,Connecting to a DB Instance over a Private Network,User Guide", "search_title":"", "metedata":[ { @@ -279,7 +279,7 @@ "code":"16", "des":"This section describes how to create a DB instance on the management console.If you need to modify your settings, click Previous.If you do not need to modify your setting", "doc_type":"usermanual", - "kw":"Step 1: Create a DB Instance,Connecting to a DB instance Over a Private Network,User Guide", + "kw":"Step 1: Create a DB Instance,Connecting to a DB Instance over a Private Network,User Guide", "search_title":"", "metedata":[ { @@ -297,7 +297,7 @@ "code":"17", "des":"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 d", "doc_type":"usermanual", - "kw":"security group,Step 2: Configure Security Group Rules,Connecting to a DB instance Over a Private Net", + "kw":"security group,Step 2: Configure Security Group Rules,Connecting to a DB Instance over a Private Net", "search_title":"", "metedata":[ { @@ -313,9 +313,9 @@ "node_id":"gaussdb_02_0009.xml", "product_code":"gaussdb", "code":"18", - "des":"GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection for enhanced secu", + "des":"GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection. SSL connections ", "doc_type":"usermanual", - "kw":"SSL connections,are encrypted,Step 3: Connect to a DB Instance Over a Private Network,Connecting to ", + "kw":"SSL connections,are encrypted,Step 3: Connect to a DB Instance over a Private Network,Connecting to ", "search_title":"", "metedata":[ { @@ -323,7 +323,7 @@ "documenttype":"usermanual" } ], - "title":"Step 3: Connect to a DB Instance Over a Private Network", + "title":"Step 3: Connect to a DB Instance over a Private Network", "githuburl":"" }, { @@ -333,7 +333,7 @@ "code":"19", "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":"Connecting to a DB Instance Over a Public Network", + "kw":"Connecting to a DB Instance over a Public Network", "search_title":"", "metedata":[ { @@ -341,7 +341,7 @@ "documenttype":"usermanual" } ], - "title":"Connecting to a DB Instance Over a Public Network", + "title":"Connecting to a DB Instance over a Public Network", "githuburl":"" }, { @@ -351,7 +351,7 @@ "code":"20", "des":"This section describes how to create a DB instance on the management console and bind an EIP to the DB instance to make the instance publicly accessible.If you are using ", "doc_type":"usermanual", - "kw":"SSL connections,are encrypted,Overview,Connecting to a DB Instance Over a Public Network,User Guide", + "kw":"SSL connections,are encrypted,Overview,Connecting to a DB Instance over a Public Network,User Guide", "search_title":"", "metedata":[ { @@ -369,7 +369,7 @@ "code":"21", "des":"This section describes how to create a DB instance on the management console.If you need to modify your settings, click Previous.If you do not need to modify your setting", "doc_type":"usermanual", - "kw":"Step 1: Create a DB Instance,Connecting to a DB Instance Over a Public Network,User Guide", + "kw":"Step 1: Create a DB Instance,Connecting to a DB Instance over a Public Network,User Guide", "search_title":"", "metedata":[ { @@ -387,7 +387,7 @@ "code":"22", "des":"You can bind an EIP to a DB instance for public access and can unbind the EIP from the DB instance if needed.Public accessibility reduces the security of DB instances. Th", "doc_type":"usermanual", - "kw":"configure security group rules,Step 2: Bind an EIP,Connecting to a DB Instance Over a Public Network", + "kw":"configure security group rules,Step 2: Bind an EIP,Connecting to a DB Instance over a Public Network", "search_title":"", "metedata":[ { @@ -405,7 +405,7 @@ "code":"23", "des":"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 da", "doc_type":"usermanual", - "kw":"security group,Step 3: Configure Security Group Rules,Connecting to a DB Instance Over a Public Netw", + "kw":"security group,Step 3: Configure Security Group Rules,Connecting to a DB Instance over a Public Netw", "search_title":"", "metedata":[ { @@ -423,7 +423,7 @@ "code":"24", "des":"GaussDB(for MySQL) is fully compatible with the MySQL protocol. Therefore, you can connect to a DB instance through a common connection or an SSL connection. SSL connecti", "doc_type":"usermanual", - "kw":"SSL connections,are encrypted,Step 4: Connect to a DB Instance Over a Public Network,Connecting to a", + "kw":"SSL connections,are encrypted,Step 4: Connect to a DB Instance over a Public Network,Connecting to a", "search_title":"", "metedata":[ { @@ -431,7 +431,7 @@ "documenttype":"usermanual" } ], - "title":"Step 4: Connect to a DB Instance Over a Public Network", + "title":"Step 4: Connect to a DB Instance over a Public Network", "githuburl":"" }, { @@ -475,7 +475,7 @@ "node_id":"gaussdb_03_0007.xml", "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 an ECS or EIP.Prepare an ECS in the same VPC subnet as the GaussDB(for MySQL) ", "doc_type":"usermanual", "kw":"Migrating Data to GaussDB(for MySQL) Using mysqldump,Data Migration,User Guide", "search_title":"", @@ -511,7 +511,7 @@ "node_id":"gaussdb_03_0011.xml", "product_code":"gaussdb", "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", + "des":"By default, a GaussDB(for MySQL) instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to the instance for public accessibi", "doc_type":"usermanual", "kw":"configure security group rules,Binding and Unbinding an EIP,Connection Management,User Guide", "search_title":"", @@ -709,7 +709,7 @@ "node_id":"gaussdb_03_0032.xml", "product_code":"gaussdb", "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", + "des":"You can change the name of a GaussDB(for MySQL) instance.The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercas", "doc_type":"usermanual", "kw":"Changing a DB Instance Name,Instance Modifications,User Guide", "search_title":"", @@ -817,7 +817,7 @@ "node_id":"gaussdb_05_2265.xml", "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", + "des":"You can manually upgrade minor versions of your instances to improve performance, add new functions, and fix bugs.The upgrade will cause the instance to reboot and interr", "doc_type":"usermanual", "kw":"Upgrading the Minor Version of a DB Instance,Instance Modifications,User Guide", "search_title":"", @@ -853,7 +853,7 @@ "node_id":"gaussdb_03_0110.xml", "product_code":"gaussdb", "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", + "des":"GaussDB(for MySQL) instances support read replicas.In read-intensive scenarios, a primary node may be unable to handle the read pressure and service performance may be af", "doc_type":"usermanual", "kw":"Introducing Read Replicas,Read Replicas,User Guide", "search_title":"", @@ -873,7 +873,7 @@ "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", + "kw":"create read replicas,Creating Read Replicas,Read Replicas,User Guide", "search_title":"", "metedata":[ { @@ -881,7 +881,7 @@ "documenttype":"usermanual" } ], - "title":"Creating a Read Replica", + "title":"Creating Read Replicas", "githuburl":"" }, { @@ -907,7 +907,7 @@ "node_id":"gaussdb_03_0113.xml", "product_code":"gaussdb", "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", + "des":"A GaussDB(for MySQL) instance consists of a primary node and multiple read replicas. In addition to automatic failover scenarios, you can perform a manual switchover to p", "doc_type":"usermanual", "kw":"Promoting a Read Replica to the Primary Node,Read Replicas,User Guide", "search_title":"", @@ -925,7 +925,7 @@ "node_id":"gaussdb_03_0114.xml", "product_code":"gaussdb", "code":"52", - "des":"You can manually delete read replicas on the Instances page.Deleted read replicas cannot be restored. Exercise caution when performing this operation.You can delete read ", + "des":"You can manually delete read replicas on the Instances page.Deleted read replicas cannot be restored. Exercise caution when performing this operation.You can only delete ", "doc_type":"usermanual", "kw":"Procedure,Deleting a Read Replica,Read Replicas,User Guide", "search_title":"", @@ -981,7 +981,7 @@ "code":"55", "des":"GaussDB(for MySQL) allows you to modify remarks of created databases.The database remarks can be empty or contain up to 512 characters.", "doc_type":"usermanual", - "kw":"GaussDB(for MySQL),Modifying Database Remarks,Database Management,User Guide", + "kw":"Modifying Database Remarks,Database Management,User Guide", "search_title":"", "metedata":[ { @@ -1141,7 +1141,7 @@ "node_id":"gaussdb_03_0051.xml", "product_code":"gaussdb", "code":"64", - "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", + "des":"You can reset the administrator password of a DB instance.If you forget the password of your database account when using GaussDB(for MySQL), you can reset the password.Yo", "doc_type":"usermanual", "kw":"reset the administrator password,Resetting the Administrator Password,Data Security,User Guide", "search_title":"", @@ -1195,7 +1195,7 @@ "node_id":"gaussdb_03_0056.xml", "product_code":"gaussdb", "code":"67", - "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(", + "des":"GaussDB(for MySQL) supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window configured for your instances.", "doc_type":"usermanual", "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", "search_title":"", @@ -1537,7 +1537,7 @@ "node_id":"gaussdb_03_0085.xml", "product_code":"gaussdb", "code":"86", - "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", + "des":"You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of metrics to be reported to Cloud ", "doc_type":"usermanual", "kw":"Cloud Eye,Configuring Displayed Metrics,Monitoring,User Guide", "search_title":"", @@ -1573,7 +1573,7 @@ "node_id":"gaussdb_03_0088.xml", "product_code":"gaussdb", "code":"88", - "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", + "des":"The Cloud Eye service monitors operating statuses of DB instances. You can view the metrics of DB instances on the management console. By monitoring system resource usage", "doc_type":"usermanual", "kw":"Cloud Eye,Viewing Monitoring Metrics,Monitoring,User Guide", "search_title":"", @@ -1663,7 +1663,7 @@ "node_id":"gaussdb_03_0017.xml", "product_code":"gaussdb", "code":"93", - "des":"You can view database logs on the GaussDB console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.", + "des":"You can view database logs on the GaussDB(for MySQL) console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.", "doc_type":"usermanual", "kw":"Viewing Logs,Logs,User Guide", "search_title":"", @@ -1807,9 +1807,9 @@ "node_id":"gaussdb_faq_0002.xml", "product_code":"gaussdb", "code":"101", - "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", + "des":"Yes. GaussDB(for MySQL) decouples storage from compute, which improves user experience in terms of high availability, backup and restoration, and upgrade and scale-out.", "doc_type":"usermanual", - "kw":"GaussDB(for MySQL),Does GaussDB(for MySQL) Support Compute and Storage Decoupling?,FAQs,User Guide", + "kw":"Does GaussDB(for MySQL) Support Decoupled Storage and Compute?,FAQs,User Guide", "search_title":"", "metedata":[ { @@ -1817,7 +1817,7 @@ "documenttype":"usermanual" } ], - "title":"Does GaussDB(for MySQL) Support Compute and Storage Decoupling?", + "title":"Does GaussDB(for MySQL) Support Decoupled Storage and Compute?", "githuburl":"" }, { @@ -1825,9 +1825,9 @@ "node_id":"gaussdb_faq_0003.xml", "product_code":"gaussdb", "code":"102", - "des":"GaussDB(for MySQL) supports up to 128 TB of data and can easily handle large amounts of data requests.", + "des":"GaussDB(for MySQL) can store up to 128 TB of data.", "doc_type":"usermanual", - "kw":"GaussDB(for MySQL),What's the Maximum Data Volume Supported by GaussDB(for MySQL)?,FAQs,User Guide", + "kw":"What's the Maximum Data Volume Supported by GaussDB(for MySQL)?,FAQs,User Guide", "search_title":"", "metedata":[ { @@ -1843,7 +1843,7 @@ "node_id":"gaussdb_faq_0005.xml", "product_code":"gaussdb", "code":"103", - "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", + "des":"During the creation of a GaussDB(for MySQL) instance, a primary node and a read replica are both created. If the primary node fails, the system automatically fails over t", "doc_type":"usermanual", "kw":"Does GaussDB(for MySQL) Support Automatic Failover?,FAQs,User Guide", "search_title":"", @@ -1879,9 +1879,9 @@ "node_id":"gaussdb_faq_0007.xml", "product_code":"gaussdb", "code":"105", - "des":"You can create a maximum of 15 read replicas for a GaussDB(for MySQL) DB instance.", + "des":"You can create a maximum of 15 read replicas for a GaussDB(for MySQL) instance.", "doc_type":"usermanual", - "kw":"GaussDB(for MySQL),How Many Read Replicas Can I Create for a GaussDB(for MySQL) DB Instance?,FAQs,Us", + "kw":"How Many Read Replicas Can I Create for a GaussDB(for MySQL) Instance?,FAQs,User Guide", "search_title":"", "metedata":[ { @@ -1889,7 +1889,7 @@ "documenttype":"usermanual" } ], - "title":"How Many Read Replicas Can I Create for a GaussDB(for MySQL) DB Instance?", + "title":"How Many Read Replicas Can I Create for a GaussDB(for MySQL) Instance?", "githuburl":"" }, { @@ -1917,7 +1917,7 @@ "code":"107", "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", + "kw":"How Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?,FAQs,User Guide", "search_title":"", "metedata":[ { @@ -1925,7 +1925,7 @@ "documenttype":"usermanual" } ], - "title":"How Can I Import the Root Certificate to a Windows or Linux OS?", + "title":"How Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?", "githuburl":"" }, { @@ -1935,7 +1935,7 @@ "code":"108", "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", + "kw":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) Instance?,FAQs,User Guide", "search_title":"", "metedata":[ { @@ -1943,7 +1943,7 @@ "documenttype":"usermanual" } ], - "title":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) DB Instance?", + "title":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) Instance?", "githuburl":"" }, { diff --git a/docs/gaussdb_mysql/umn/CLASS.TXT.json b/docs/gaussdb_mysql/umn/CLASS.TXT.json index a87fa91d7..d6b3ad46c 100644 --- a/docs/gaussdb_mysql/umn/CLASS.TXT.json +++ b/docs/gaussdb_mysql/umn/CLASS.TXT.json @@ -27,7 +27,7 @@ "code":"3" }, { - "desc":"GaussDB(for MySQL) is an enterprise-class cloud database that uses a decoupled compute and storage architecture.Mass storage with 128 TB capacity and no sharding required", + "desc":"GaussDB(for MySQL) is an enterprise-grade cloud database with decoupled compute and storage.Mass storage with 128 TB capacity and no sharding requiredEasy-to-use, fully c", "product_code":"gaussdb", "title":"Product Benefits", "uri":"gaussdb_01_0002.html", @@ -45,7 +45,7 @@ "code":"5" }, { - "desc":"GaussDB(for MySQL) instance specifications are listed in the following table and vary according to actual situations.", + "desc":"GaussDB(for MySQL) instance specifications are listed in the following tables and vary according to actual situations.", "product_code":"gaussdb", "title":"DB Instance Specifications", "uri":"gaussdb_01_0004.html", @@ -101,14 +101,14 @@ { "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":"Getting Started with GaussDB(for MySQL)", + "title":"Getting Started", "uri":"gaussdb_02_0000.html", "doc_type":"usermanual", "p_code":"", "code":"12" }, { - "desc":"You can connect a DB instance over a private or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ECS is in the sam", + "desc":"You can connect a DB instance over a private or public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ECS is in the same ", "product_code":"gaussdb", "title":"Connecting to a DB Instance", "uri":"quick_start.html", @@ -119,7 +119,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":"Connecting to a DB instance Over a Private Network", + "title":"Connecting to a DB Instance over a Private Network", "uri":"gaussdb_02_0005.html", "doc_type":"usermanual", "p_code":"12", @@ -153,9 +153,9 @@ "code":"17" }, { - "desc":"GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection for enhanced secu", + "desc":"GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection. SSL connections ", "product_code":"gaussdb", - "title":"Step 3: Connect to a DB Instance Over a Private Network", + "title":"Step 3: Connect to a DB Instance over a Private Network", "uri":"gaussdb_02_0009.html", "doc_type":"usermanual", "p_code":"14", @@ -164,7 +164,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":"Connecting to a DB Instance Over a Public Network", + "title":"Connecting to a DB Instance over a Public Network", "uri":"gaussdb_02_0010.html", "doc_type":"usermanual", "p_code":"12", @@ -209,7 +209,7 @@ { "desc":"GaussDB(for MySQL) is fully compatible with the MySQL protocol. Therefore, you can connect to a DB instance through a common connection or an SSL connection. SSL connecti", "product_code":"gaussdb", - "title":"Step 4: Connect to a DB Instance Over a Public Network", + "title":"Step 4: Connect to a DB Instance over a Public Network", "uri":"gaussdb_02_0014.html", "doc_type":"usermanual", "p_code":"19", @@ -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 an ECS or EIP.Prepare an ECS in the same VPC subnet as the GaussDB(for MySQL) ", "product_code":"gaussdb", "title":"Migrating Data to GaussDB(for MySQL) Using mysqldump", "uri":"gaussdb_03_0007.html", @@ -252,7 +252,7 @@ "code":"28" }, { - "desc":"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", + "desc":"By default, a GaussDB(for MySQL) instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to the instance for public accessibi", "product_code":"gaussdb", "title":"Binding and Unbinding an EIP", "uri":"gaussdb_03_0011.html", @@ -351,7 +351,7 @@ "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", + "desc":"You can change the name of a GaussDB(for MySQL) instance.The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercas", "product_code":"gaussdb", "title":"Changing a DB Instance Name", "uri":"gaussdb_03_0032.html", @@ -405,7 +405,7 @@ "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", + "desc":"You can manually upgrade minor versions of your instances to improve performance, add new functions, and fix bugs.The upgrade will cause the instance to reboot and interr", "product_code":"gaussdb", "title":"Upgrading the Minor Version of a DB Instance", "uri":"gaussdb_05_2265.html", @@ -423,7 +423,7 @@ "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", + "desc":"GaussDB(for MySQL) instances support read replicas.In read-intensive scenarios, a primary node may be unable to handle the read pressure and service performance may be af", "product_code":"gaussdb", "title":"Introducing Read Replicas", "uri":"gaussdb_03_0110.html", @@ -434,7 +434,7 @@ { "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", "product_code":"gaussdb", - "title":"Creating a Read Replica", + "title":"Creating Read Replicas", "uri":"gaussdb_03_0111.html", "doc_type":"usermanual", "p_code":"47", @@ -450,7 +450,7 @@ "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", + "desc":"A GaussDB(for MySQL) instance consists of a primary node and multiple read replicas. In addition to automatic failover scenarios, you can perform a manual switchover to p", "product_code":"gaussdb", "title":"Promoting a Read Replica to the Primary Node", "uri":"gaussdb_03_0113.html", @@ -459,7 +459,7 @@ "code":"51" }, { - "desc":"You can manually delete read replicas on the Instances page.Deleted read replicas cannot be restored. Exercise caution when performing this operation.You can delete read ", + "desc":"You can manually delete read replicas on the Instances page.Deleted read replicas cannot be restored. Exercise caution when performing this operation.You can only delete ", "product_code":"gaussdb", "title":"Deleting a Read Replica", "uri":"gaussdb_03_0114.html", @@ -567,7 +567,7 @@ "code":"63" }, { - "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", + "desc":"You can reset the administrator password of a DB instance.If you forget the password of your database account when using GaussDB(for MySQL), you can reset the password.Yo", "product_code":"gaussdb", "title":"Resetting the Administrator Password", "uri":"gaussdb_03_0051.html", @@ -594,7 +594,7 @@ "code":"66" }, { - "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(", + "desc":"GaussDB(for MySQL) supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window configured for your instances.", "product_code":"gaussdb", "title":"Working with Backups", "uri":"gaussdb_03_0056.html", @@ -765,7 +765,7 @@ "code":"85" }, { - "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", + "desc":"You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of metrics to be reported to Cloud ", "product_code":"gaussdb", "title":"Configuring Displayed Metrics", "uri":"gaussdb_03_0085.html", @@ -783,7 +783,7 @@ "code":"87" }, { - "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", + "desc":"The Cloud Eye service monitors operating statuses of DB instances. You can view the metrics of DB instances on the management console. By monitoring system resource usage", "product_code":"gaussdb", "title":"Viewing Monitoring Metrics", "uri":"gaussdb_03_0088.html", @@ -828,7 +828,7 @@ "code":"92" }, { - "desc":"You can view database logs on the GaussDB console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.", + "desc":"You can view database logs on the GaussDB(for MySQL) console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.", "product_code":"gaussdb", "title":"Viewing Logs", "uri":"gaussdb_03_0017.html", @@ -900,16 +900,16 @@ "code":"100" }, { - "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", + "desc":"Yes. GaussDB(for MySQL) decouples storage from compute, which improves user experience in terms of high availability, backup and restoration, and upgrade and scale-out.", "product_code":"gaussdb", - "title":"Does GaussDB(for MySQL) Support Compute and Storage Decoupling?", + "title":"Does GaussDB(for MySQL) Support Decoupled Storage and Compute?", "uri":"gaussdb_faq_0002.html", "doc_type":"usermanual", "p_code":"100", "code":"101" }, { - "desc":"GaussDB(for MySQL) supports up to 128 TB of data and can easily handle large amounts of data requests.", + "desc":"GaussDB(for MySQL) can store up to 128 TB of data.", "product_code":"gaussdb", "title":"What's the Maximum Data Volume Supported by GaussDB(for MySQL)?", "uri":"gaussdb_faq_0003.html", @@ -918,7 +918,7 @@ "code":"102" }, { - "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", + "desc":"During the creation of a GaussDB(for MySQL) instance, a primary node and a read replica are both created. If the primary node fails, the system automatically fails over t", "product_code":"gaussdb", "title":"Does GaussDB(for MySQL) Support Automatic Failover?", "uri":"gaussdb_faq_0005.html", @@ -936,9 +936,9 @@ "code":"104" }, { - "desc":"You can create a maximum of 15 read replicas for a GaussDB(for MySQL) DB instance.", + "desc":"You can create a maximum of 15 read replicas for a GaussDB(for MySQL) instance.", "product_code":"gaussdb", - "title":"How Many Read Replicas Can I Create for a GaussDB(for MySQL) DB Instance?", + "title":"How Many Read Replicas Can I Create for a GaussDB(for MySQL) Instance?", "uri":"gaussdb_faq_0007.html", "doc_type":"usermanual", "p_code":"100", @@ -956,7 +956,7 @@ { "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", "product_code":"gaussdb", - "title":"How Can I Import the Root Certificate to a Windows or Linux OS?", + "title":"How Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?", "uri":"gaussdb_faq_0010.html", "doc_type":"usermanual", "p_code":"100", @@ -965,7 +965,7 @@ { "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 ", "product_code":"gaussdb", - "title":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) DB Instance?", + "title":"What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) Instance?", "uri":"gaussdb_faq_0009.html", "doc_type":"usermanual", "p_code":"100", diff --git a/docs/gaussdb_mysql/umn/change_history.html b/docs/gaussdb_mysql/umn/change_history.html index fa469073d..6e02d9925 100644 --- a/docs/gaussdb_mysql/umn/change_history.html +++ b/docs/gaussdb_mysql/umn/change_history.html @@ -8,7 +8,12 @@ -

2024-08-08

+

2024-12-10

+ +

Optimized the content in Backup Space and Billing.

+ + +

2024-08-08

diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0001.html b/docs/gaussdb_mysql/umn/gaussdb_01_0001.html index fbac99231..55077fe76 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0001.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0001.html @@ -1,8 +1,8 @@

Basic Concepts

-

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

-
  • Cluster: GaussDB(for MySQL) uses the cluster architecture, with one primary node and multiple read replicas.
  • Region: A region is a physical data center. Generally, GaussDB(for MySQL) DB instances and ECSs must be located in the same region for high access performance.
  • Availability zone (AZ): An AZ contains one or multiple physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple instances. An AZ is a geographic location with independent power supply and network facilities in a region.

    AZs are physically isolated but interconnected over an intranet. Each AZ provides cost-effective and low-latency network connections that are unaffected by faults that may occur in other AZs. As a result, provisioning GaussDB(for MySQL) DB instances in separate AZs protects your applications against local faults that occur in a single location. AZs within the same region have no functional differences.

    +

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

    +
    • Cluster: GaussDB(for MySQL) uses the cluster architecture, with one primary node and multiple read replicas.
    • Region: A region is a physical data center. Generally, GaussDB(for MySQL) instances and ECSs must be located in the same region for high access performance.
    • Availability zone (AZ): An AZ contains one or multiple physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple instances. An AZ is a geographic location with independent power supply and network facilities in a region.

      AZs are physically isolated but interconnected over an intranet. Each AZ provides cost-effective and low-latency network connections that are unaffected by faults that may occur in other AZs. As a result, provisioning GaussDB(for MySQL) instances in separate AZs protects your applications against local faults that occur in a single location. AZs within the same region have no functional differences.

    • Instance class: resource configuration of each node, for example, 16 vCPUs and 64 GB.
    diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0002.html b/docs/gaussdb_mysql/umn/gaussdb_01_0002.html index cd80c219f..ff9e8f442 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0002.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0002.html @@ -1,9 +1,9 @@

    Product Benefits

    -

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

    +

    GaussDB(for MySQL) is an enterprise-grade cloud database with decoupled compute and storage.

    Requirements

    -
    Table 1 Requirements

    Requirements

    +
    diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0004.html b/docs/gaussdb_mysql/umn/gaussdb_01_0004.html index 5862aae1f..e476f0a87 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0004.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0004.html @@ -1,11 +1,11 @@

    DB Instance Specifications

    -

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

    +

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

    -
    Table 1 Requirements

    Requirement

    Description
    Table 1 x86 instance specifications

    Instance Specifications

    +
    - @@ -47,9 +47,9 @@
    Table 1 x86 instance specifications

    Instance Specifications

    vCPUs

    +

    vCPUs

    Memory (GB)

    -
    Table 2 Kunpeng instance specifications

    Instance Specifications

    +
    - diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0005.html b/docs/gaussdb_mysql/umn/gaussdb_01_0005.html index 87974fea9..fba297559 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0005.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0005.html @@ -1,7 +1,7 @@

    DB Engines and Versions

    -

    Table 1 lists the DB engines and versions supported by GaussDB(for MySQL).

    +

    Table 1 lists the DB engines and versions supported by GaussDB(for MySQL).

    Table 2 Kunpeng instance specifications

    Instance Specifications

    vCPUs

    +

    vCPUs

    Memory (GB)
    diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0008.html b/docs/gaussdb_mysql/umn/gaussdb_01_0008.html index 6dc1303f3..493043b9f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0008.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0008.html @@ -1,7 +1,7 @@

    Constraints

    -

    Table 1 shows the constraints designed to ensure the stability and security of GaussDB(for MySQL).

    +

    Table 1 shows the constraints designed to ensure the stability and security of GaussDB(for MySQL).

    Table 1 DB engines and versions

    DB Engine
    @@ -9,15 +9,15 @@ - - - - - - - - - diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0009.html b/docs/gaussdb_mysql/umn/gaussdb_01_0009.html index dee52f312..03a70eaea 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0009.html @@ -1,7 +1,7 @@

    Related Services

    -

    The following figure shows the relationship between GaussDB(for MySQL) and other services.

    +

    The following figure shows the relationship between GaussDB(for MySQL) and other services.

    Table 1 Function constraints

    Function

    GaussDB(for MySQL) access

    +

    GaussDB(for MySQL) access

    • If GaussDB(for MySQL) DB instances are not bound with EIPs, the DB instances must be in the same VPC subnet as the ECSs associated with these instances.
    • Security group rules must be added to allow ECSs to access GaussDB(for MySQL) DB instances.

      By default, a GaussDB(for MySQL) DB instance cannot be accessed by an ECS in a different security group. To allow it, you must add an inbound rule to the GaussDB(for MySQL) security group.

      -
    • The default GaussDB(for MySQL) DB instance port is 3306. You can change it if you want to access GaussDB(for MySQL) through another port.
    +
    • If GaussDB(for MySQL) instances are not bound with EIPs, the instances must be in the same VPC subnet as the ECSs associated with these instances.
    • Security group rules must be added to allow ECSs to access GaussDB(for MySQL) instances.

      By default, a GaussDB(for MySQL) instance cannot be accessed by an ECS in a different security group. To allow it, you must add an inbound rule to the GaussDB(for MySQL) security group.

      +
    • The default GaussDB(for MySQL) instance port is 3306. You can change it if you want to access GaussDB(for MySQL) through another port.

    Deployment

    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.

    +

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

    Administrator root permission

    @@ -27,22 +27,22 @@

    Database parameter modification

    Most parameters can be modified on the GaussDB(for MySQL) console.

    +

    Most parameters can be modified on the GaussDB(for MySQL) console.

    Data migration

    The mysqldump tool is used to migrate data to GaussDB(for MySQL).

    +

    The mysqldump tool is used to migrate data to GaussDB(for MySQL).

    GaussDB(for MySQL) instance reboot

    +

    GaussDB(for MySQL) instance reboot

    GaussDB(for MySQL) instances cannot be rebooted through commands. They must be rebooted on the GaussDB(for MySQL) console.

    +

    GaussDB(for MySQL) instances cannot be rebooted through commands. They must be rebooted on the GaussDB(for MySQL) console.

    GaussDB(for MySQL) backup files

    +

    GaussDB(for MySQL) backup files

    GaussDB(for MySQL) backup files are stored in OBS buckets and are not visible to users.

    +

    GaussDB(for MySQL) backup files are stored in OBS buckets and are not visible to users.
    @@ -11,22 +11,22 @@ - - - - -
    Table 1 Related services

    Service Name

    Elastic Cloud Service (ECS)

    Enables you to access GaussDB(for MySQL) DB instances through an ECS to reduce application response time and public network traffic fees.

    +

    Enables you to access GaussDB(for MySQL) instances through an ECS to reduce application response time and public network traffic fees.

    Virtual Private Cloud (VPC)

    Isolates your networks and controls access to your GaussDB(for MySQL) DB instances.

    +

    Isolates your networks and controls access to your GaussDB(for MySQL) instances.

    Object Storage Service (OBS)

    Stores automated and manual backups of your GaussDB(for MySQL) DB instances.

    +

    Stores automated and manual backups of your GaussDB(for MySQL) instances.

    Cloud Eye

    Acts as an open monitoring platform that monitors GaussDB(for MySQL) resources in real time. It reports alarms and issues warnings promptly to ensure that services are running properly.

    +

    Acts as an open monitoring platform that monitors GaussDB(for MySQL) resources in real time. It reports alarms and issues warnings promptly to ensure that services are running properly.

    Cloud Trace Service (CTS)

    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0000.html b/docs/gaussdb_mysql/umn/gaussdb_02_0000.html index ef3935383..930f20192 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0000.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0000.html @@ -1,14 +1,14 @@ -

    Getting Started with GaussDB(for MySQL)

    +

    Getting Started

    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0004.html b/docs/gaussdb_mysql/umn/gaussdb_02_0004.html index 0211720dd..7c3676511 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0004.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0004.html @@ -24,7 +24,7 @@

    DB Engine

    GaussDB(for MySQL)

    +

    GaussDB(for MySQL)

    DB Engine Version

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

    Parameter

    +
    - @@ -61,8 +61,8 @@ -
    Table 2 Specifications and storage

    Parameter

    Description

    +

    Description

    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.

    +

    A GaussDB(for MySQL) instance 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 Read Replicas.

    Storage

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

    Parameter

    +
    - -
    Table 3 Network

    Parameter

    Description

    +

    Description

    VPC

    A dedicated virtual network in which your DB instances are located. It isolates networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see "Creating a VPC" in the Virtual Private Cloud User Guide.

    -

    If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.

    +

    If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.

    Subnet

    @@ -94,15 +94,15 @@

    Security Group

    Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.

    -

    If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.

    +

    Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.

    +

    If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.
    -
    Table 4 Database configuration

    Parameter

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

    Parameter

    Description

    -
    Table 5 Parameter template

    Parameter

    +
    - @@ -167,7 +167,7 @@ diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0005.html b/docs/gaussdb_mysql/umn/gaussdb_02_0005.html index 2d0e816ef..584666c09 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0005.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0005.html @@ -1,6 +1,6 @@ -

    Connecting to a DB instance Over a Private Network

    +

    Connecting to a DB Instance over a Private Network

    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0006.html b/docs/gaussdb_mysql/umn/gaussdb_02_0006.html index 80e656076..e72b94f72 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0006.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0006.html @@ -6,14 +6,14 @@

    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 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 1: Create a DB instance. Confirm the specifications, 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 associated with the DB instance.
            • ECS: The default security group rule allows all outgoing data packets. In this case, 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 f88a2fba1..5d558ccb4 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html @@ -3,16 +3,16 @@

    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 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.
      +
      • 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 associated with the DB instance.
        • 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.

    • By default, you can create a maximum of 500 security group rules.
    • To prevent high network latency for the first packet, you are advised to create a maximum of 50 rules for each security group.
    • 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.

    To ensure the security of your data and DB instances, you are advised to use the principle of least privilege for database access. Change the database port (default value: 3306), and set the IP address to the remote server's address or an IP address on the remote server's smallest subnet so that access to the remote server is limited.

    -

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

    +

    The default value of Source is 0.0.0.0/0, indicating that GaussDB(for MySQL) instances in the security group can be accessed from any IP address.

    -

    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 Databases, click GaussDB(for MySQL).
    4. On the Instances 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 Databases, click GaussDB(for MySQL).
      4. On the Instances page, click the instance name to go to the Basic Information page.
      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 5 Parameter template

    Parameter

    Description

    +

    Description
    @@ -72,7 +72,7 @@ diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0009.html b/docs/gaussdb_mysql/umn/gaussdb_02_0009.html index 99b9bc51a..59ee7d6e2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0009.html @@ -1,7 +1,7 @@ -

    Step 3: Connect to a DB Instance Over a Private Network

    -

    GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection for enhanced security. SSL connections are encrypted.

    +

    Step 3: Connect to a DB Instance over a Private Network

    +

    GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection. SSL connections are encrypted.

    Prerequisites

    1. Log in to the ECS.

      • For details on how to create and log in to an ECS, see "Creating an ECS" and "Logging In an ECS" in the Elastic Cloud Server User Guide.

      • To connect to a DB instance through an ECS, you must ensure that:
        • The ECS and DB instance are in the same VPC.
        • The ECS must be allowed by the security group to access DB instances.
          • If the security group with which the target DB instance associated is the default security group, you do not need to configure security group rules.
          • If the security group with which the target DB instance associated is not the default security group, check whether the security group rules allow the ECS to connect to the DB instance. For details, see Step 2: Configure Security Group Rules.

            If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.

            If the security group rules do not allow the access from the ECS, you need to add a security group rule. The ECS must be allowed by the security group to access DB instances.

            @@ -9,7 +9,7 @@
      • Use a database client to connect to the target DB instance.

        You can use a database client to connect to the DB instance in the Linux or Windows OS.

        -
        • In the Linux OS, install the MySQL client on the ECS or other device that can access the DB instance. It is recommended that you download a MySQL client running a version later than that of the DB instance.

          For details about how to obtain and install the MySQL client, see How Can I Install the MySQL Client?

          +
          • In the Linux OS, install the MySQL client on the device that can access GaussDB(for MySQL). It is recommended that you download a MySQL client running a version later than that of the DB instance.

            For details about how to obtain and install the MySQL client, see How Can I Install the MySQL Client?

          @@ -31,7 +31,7 @@
    - @@ -56,7 +56,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

    • -

    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 Databases, click GaussDB(for MySQL).
    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 Databases, click GaussDB(for MySQL).
      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 Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?

      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 1 Inbound rule parameter description

    Parameter

    Host

    Private IP address for write of the target DB instance. To view the private address of the target DB instance, perform the following steps:
    1. Log in to the GaussDB(for MySQL) console.
    2. Select the region in which the DB instance is located.
    3. Click the target DB instance to go to the Basic Information page.
    4. In the Network Information area, view the private IP address for write.
    +
    Private IP address for write of the target DB instance. To view the private address of the target DB instance, perform the following steps:
    1. Log in to the GaussDB(for MySQL) console.
    2. Select the region in which the DB instance is located.
    3. Click the target DB instance to go to the Basic Information page.
    4. In the Network Information area, view the private IP address for write.
    - -
    Table 2 Parameter description

    Parameter

    @@ -79,7 +79,7 @@

    <userName>

    Username of the GaussDB(for MySQL) administrator account. The default username is root.

    +

    Username of the GaussDB(for MySQL) administrator account. The default username is root.

    <caName>

    @@ -99,7 +99,7 @@ diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0010.html b/docs/gaussdb_mysql/umn/gaussdb_02_0010.html index f517c5344..c20073ad2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0010.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0010.html @@ -1,6 +1,6 @@ -

    Connecting to a DB Instance Over a Public Network

    +

    Connecting to a DB Instance over a Public Network

    diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0012.html b/docs/gaussdb_mysql/umn/gaussdb_02_0012.html index 4670b3b31..e8d569418 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0012.html @@ -24,7 +24,7 @@

    DB Engine

    GaussDB(for MySQL)

    +

    GaussDB(for MySQL)

    DB Engine Version

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

    Parameter

    +
    - @@ -61,8 +61,8 @@ -
    Table 2 Specifications and storage

    Parameter

    Description

    +

    Description

    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.

    +

    A GaussDB(for MySQL) instance 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 Read Replicas.

    Storage

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

    Parameter

    +
    - -
    Table 3 Network

    Parameter

    Description

    +

    Description

    VPC

    A dedicated virtual network in which your DB instances are located. It isolates networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see "Creating a VPC" in the Virtual Private Cloud User Guide.

    -

    If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.

    +

    If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.

    Subnet

    @@ -94,15 +94,15 @@

    Security Group

    Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.

    -

    If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.

    +

    Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.

    +

    If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.
    -
    Table 4 Database configuration

    Parameter

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

    Parameter

    Description

    -
    Table 5 Parameter template

    Parameter

    +
    - @@ -167,7 +167,7 @@ diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0013.html b/docs/gaussdb_mysql/umn/gaussdb_02_0013.html index 18eaf48d5..252e1abb3 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0013.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0013.html @@ -8,10 +8,10 @@

    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.

    • By default, you can create a maximum of 500 security group rules.
    • To prevent high network latency for the first packet, you are advised to create a maximum of 50 rules for each security group.
    • 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.

    To ensure the security of your data and DB instances, you are advised to use the principle of least privilege for database access. Change the database port (default value: 3306), and set the IP address to the remote server's address or an IP address on the remote server's smallest subnet so that access to the remote server is limited.

    -

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

    +

    The default value of Source is 0.0.0.0/0, indicating that GaussDB(for MySQL) instances in the security group can be accessed from any IP address.

    -

    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 Databases, click GaussDB(for MySQL).
    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 Databases, click GaussDB(for MySQL).
      4. On the Instances page, click the instance name to go to the Basic Information page.
      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 5 Parameter template

    Parameter

    Description

    +

    Description
    @@ -55,7 +55,7 @@ diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0014.html b/docs/gaussdb_mysql/umn/gaussdb_02_0014.html index 78cabafbe..dc70d9f80 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0014.html @@ -1,7 +1,7 @@ -

    Step 4: Connect to a DB Instance Over a Public Network

    -

    GaussDB(for MySQL) is fully compatible with the MySQL protocol. Therefore, you can connect to a DB instance through a common connection or an SSL connection. SSL connections are encrypted.

    +

    Step 4: Connect to a DB Instance over a Public Network

    +

    GaussDB(for MySQL) is fully compatible with the MySQL protocol. Therefore, you can connect to a DB instance through a common connection or an SSL connection. SSL connections are encrypted.

    Prerequisites

    1. Bind an EIP to the target DB instance and configure security group rules.
      1. Bind an EIP to the target DB instance.

        For details about how to bind an EIP, see Step 2: Bind an EIP.

      2. Obtain the IP address of the local device.
      3. Configure security group rules.

        Add the IP address and port obtained in 1.b to the inbound rule of the security group.

        For details about how to configure a security group rule, see Step 3: Configure Security Group Rules.

        @@ -14,7 +14,7 @@

    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
      +

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

    +

    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

    @@ -56,7 +56,7 @@

    -

    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 Databases, click GaussDB(for MySQL).
    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 Databases, click GaussDB(for MySQL).
      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 Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?

      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 (EIP) 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>

        @@ -76,7 +76,7 @@

        <userName>

        Username of the GaussDB(for MySQL) database administrator account. The default username is root.

        +

        Username of the GaussDB(for MySQL) administrator account. The default username is root.

        <caName>

        @@ -99,7 +99,7 @@ diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html index 1fac6e8bb..a5810c51c 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html @@ -3,9 +3,9 @@

        Step 2: Bind an EIP

        Scenarios

        You can bind an EIP to a DB instance for public access and can unbind the EIP from the DB instance if needed.

        -

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

        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 your 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 Databases, click GaussDB(for MySQL).
        4. On the Instances 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.

          +

          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 Databases, click GaussDB(for MySQL).
          4. On the Instances page, click the instance name to go to the Basic Information page.
          5. In the Network Information area, click Bind next to Private IP Address.
          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.
          @@ -13,7 +13,7 @@
          diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0016.html b/docs/gaussdb_mysql/umn/gaussdb_02_0016.html index 51cc849c0..e9a876d2d 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0016.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0016.html @@ -2,16 +2,16 @@

          Overview

          Scenarios

          This section describes how to create a DB instance on the management console and bind an EIP to the DB instance to make the instance publicly accessible.

          -

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

          +

          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
          -
          • 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.
          +
          • Step 1: Create a DB instance. Confirm the specifications, 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 4069c9d44..215725033 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0007.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0007.html @@ -1,19 +1,19 @@ -

          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.

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

              +

              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.

              +
              1. Prepare an ECS in the same VPC subnet as the GaussDB(for MySQL) instance or bind an EIP to the GaussDB(for MySQL) instance.
                • 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 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.

                +

                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.

              -

              Exporting Data

              Before migrating data to GaussDB(for MySQL), you need to export data first.

              +

              Exporting Data

              Before migrating data to GaussDB(for MySQL), you need to export data first.

              • The export tool must match the DB engine version.
              • Database migration is performed offline. Before the migration, you must stop any applications using the source database.
              -
              1. Log in to the prepared ECS or device that can access GaussDB(for MySQL) DB instances.
              2. Use the mysqldump tool to export metadata into an SQL file.

                MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.

                +
                1. Log in to the prepared ECS or device that can access GaussDB(for MySQL) instances.
                2. Use the mysqldump tool to export metadata into an SQL file.

                  MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.

                  mysqldump --databases <DB_NAME> --single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF -u <DB_USER> -p -h <DB_ADDRESS> -P <DB_PORT> |sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' > <BACKUP_FILE>

                  • DB_NAME indicates the name of the database to be migrated.
                  • DB_USER indicates the database username.
                  • DB_ADDRESS indicates the database address.
                  • DB_PORT indicates the database port.
                  • BACKUP_FILE indicates the name of the file to which the data will be exported.
                  @@ -22,27 +22,27 @@

                  mysqldump --databases gaussdb --single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF -u root -p -h 192.168.151.18 -P 3306 |sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' > dump-defs.sql

                  Enter password:

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

                  -

                3. Use the mysqldump tool to export data into an SQL file.

                  MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.

                  +

                4. Use the mysqldump tool to export data into an SQL file.

                  MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.

                  mysqldump --databases <DB_NAME> --single-transaction --hex-blob --set-gtid-purged=OFF --no-create-info --skip-triggers -u <DB_USER> -p -h <DB_ADDRESS> -P <DB_PORT> -r <BACKUP_FILE>

                  For details on the parameters in the preceding command, see 2.

                  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.

                +

                Importing Data

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

                If the source database contains triggers, storage processes, functions, or event invocation, you must set log_bin_trust_function_creators to ON for the destination database before importing data.

                -
                1. Import metadata into GaussDB(for MySQL).

                  Use the MySQL tool to connect to the GaussDB(for MySQL) DB instance, enter the password, and run the following command to import metadata:

                  +
                  1. Import metadata into GaussDB(for MySQL).

                    Use the MySQL tool to connect to the GaussDB(for MySQL) instance, enter the password, and run the following command to import metadata:

                    mysql -f -h <DB_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-defs.sql

                    -
                    • DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) DB instance.
                    • DB_PORT indicates the GaussDB(for MySQL) DB instance port.
                    • BACKUP_DIR indicates the directory where dump-defs.sql is stored.
                    +
                    • DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) instance.
                    • DB_PORT indicates the GaussDB(for MySQL) instance port.
                    • BACKUP_DIR indicates the directory where dump-defs.sql is stored.

                    Example:

                    mysql -f -h 172.16.66.198 -P 3306 -u root -p < dump-defs.sql

                    Enter password:

                    -

                  2. Import data into GaussDB(for MySQL).

                    mysql -f -h <DB_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-data.sql

                    -
                    • DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) DB instance.
                    • DB_PORT indicates the GaussDB(for MySQL) DB instance port.
                    • BACKUP_DIR indicates the directory where dump-data.sql is stored.
                    +

                  3. Import data into GaussDB(for MySQL).

                    mysql -f -h <DB_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-data.sql

                    +
                    • DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) instance.
                    • DB_PORT indicates the GaussDB(for MySQL) instance port.
                    • BACKUP_DIR indicates the directory where dump-data.sql is stored.

                    Example:

                    mysql -f -h 172.16.66.198 -P 3306 -u root -p < dump-data.sql

                    Enter password:

                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0009.html b/docs/gaussdb_mysql/umn/gaussdb_03_0009.html index ce047b944..d82bc8c4f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0009.html @@ -6,7 +6,7 @@
                    • Introducing Read Replicas
                      • -
                    • Creating a Read Replica
                      +
                    • Creating Read Replicas
                    • Managing a Read Replica
                      • diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0011.html b/docs/gaussdb_mysql/umn/gaussdb_03_0011.html index 2befa1cfd..68a153414 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0011.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0011.html @@ -1,13 +1,13 @@

                      Binding and Unbinding an EIP

                      -

                      Scenarios

                      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 accessibility and can unbind the EIP from the DB instance as required.

                      +

                      Scenarios

                      By default, a GaussDB(for MySQL) instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to the instance for public accessibility and can unbind the EIP from the instance as required.

                      To ensure that the database can be accessed, the security group used by the database must have the permission to access the database port. For example, if the database port is 3306, ensure that the security group has the permission to access port 3306.

                      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 Databases, click GaussDB(for MySQL).
                      4. On the Instances 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.

                        +

                        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 Databases, click GaussDB(for MySQL).
                        4. On the Instances page, click the instance name to go to the Basic Information page.
                        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.

                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html index 11d3064a5..106adbe96 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html @@ -5,7 +5,7 @@

                        Constraints

                        Changing the database port of a DB instance will only affect access through its IP address. If a DB instance is accessed through a proxy instance, the database port of the proxy instance cannot be changed, which defaults to 3306.

                        -

                        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 Databases, click GaussDB(for MySQL).
                        4. On the Instances page, click the target DB instance to go to the Basic Information page.
                        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.
                              +

                              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 Databases, click GaussDB(for MySQL).
                              4. On the Instances page, click the instance name to go to the Basic Information page.
                              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 reserved by the system.
                                • 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 .
                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0014.html b/docs/gaussdb_mysql/umn/gaussdb_03_0014.html index 23b613869..c2c18904e 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0014.html @@ -1,9 +1,9 @@

                                Key Operations Supported by CTS

                                -

                                Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for further querying, auditing, and backtracking. Table 1 lists the supported operations.

                                +

                                Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for further querying, auditing, and backtracking. Table 1 lists the supported operations.

                                -
                                Table 1 GaussDB(for MySQL) operations recorded by CTS

                                Operation

                                +
                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0017.html b/docs/gaussdb_mysql/umn/gaussdb_03_0017.html index 860a7a008..546b74c30 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0017.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0017.html @@ -1,7 +1,7 @@

                                Viewing Logs

                                -

                                You can view database logs on the GaussDB console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.

                                +

                                You can view database logs on the GaussDB(for MySQL) console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.

                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html index 594f680c7..78fe81180 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html @@ -2,10 +2,10 @@

                                Viewing Slow Query Logs

                                Scenarios

                                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 slowly and optimize the statements.

                                -
                                GaussDB(for MySQL) supports the following statement types:
                                • SELECT
                                • INSERT
                                • UPDATE
                                • DELETE
                                • CREATE
                                • ALTER
                                • DROP
                                +
                                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 Databases, click GaussDB(for MySQL).
                                4. On the Instances 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 Databases, click GaussDB(for MySQL).
                                  4. On the Instances 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_0032.html b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html index 051e879bb..cc72d1ba3 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html @@ -1,7 +1,7 @@

                                Changing a DB Instance Name

                                -

                                Scenarios

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

                                +

                                Scenarios

                                You can change the name of a GaussDB(for MySQL) 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 Databases, click GaussDB(for MySQL).
                                4. On the Instances page, locate the instance name and click in the Name/ID column to edit the instance name.

                                  • The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.
                                  • When changing the instance name, you can determine whether to select Change node names synchronously as required. If this option is selected, the names of the corresponding nodes are changed when the instance name is changed. If this option is not selected, only the instance name is changed, and the corresponding node names are not changed.
                                  • If you want to submit the change, click OK. If you want to cancel the change, click Cancel.

                                5. View the result of the change on the Basic Information page.
                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0047.html b/docs/gaussdb_mysql/umn/gaussdb_03_0047.html index fe92c766b..35d95179f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0047.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0047.html @@ -7,7 +7,7 @@

                                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 Databases, click GaussDB(for MySQL).
                                4. On the Instances 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 Instances 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 Databases, click GaussDB(for MySQL).
                                4. On the Instances 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 Instances page later to check that the deletion is successful.
                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html index 5c4520f77..910f214b1 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html @@ -2,21 +2,21 @@

                                Resetting the Administrator Password

                                Scenarios

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

                                +

                                If you forget the password of your database account when using GaussDB(for MySQL), you can reset the password.

                                You cannot reset the administrator password under the following circumstances:

                                • 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 Databases, click GaussDB(for MySQL).
                                4. On the Instances 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 Databases, click GaussDB(for MySQL).
                                  4. On the Instances page, locate the instance for which you want to change the password 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 Databases, click GaussDB(for MySQL).
                                  4. On the Instances 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 Databases, 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 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.
                                      +
                                      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_0056.html b/docs/gaussdb_mysql/umn/gaussdb_03_0056.html index 21c71566a..3a59c5743 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0056.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0056.html @@ -2,7 +2,7 @@

                                    Working with Backups

                                    GaussDB(for MySQL) supports backups and restorations to ensure data reliability.

                                    -

                                    Automated Backups

                                    Automated backups are created during the backup time window of your DB instances. GaussDB(for MySQL) saves automated backups based on the retention period you have specified. If necessary, you can restore to any point in time during your backup retention period.

                                    +

                                    Automated Backups

                                    Automated backups are created during the backup time window configured for your instances. GaussDB(for MySQL) saves automated backups based on the retention period you have specified. If necessary, you can restore to any point in time during your backup retention period.

                                    Manual Backups

                                    Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually.

                                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html index ead577874..c3cce5be0 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html @@ -7,8 +7,8 @@

                                    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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances 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 Backups 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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances page, click the target DB instance.
                                    5. On the Backups page, click Create Backup. In the displayed dialog box, enter a backup name and a description, and click OK. If you want to cancel the backup creation task, click Cancel.

                                      • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                      • The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
                                      • The time required for creating a manual backup depends on the data volume of the DB instance.
                                      -

                                    6. After a manual backup has been created, you can view and manage it on the Backups 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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances page, click the instance name.
                                    5. On the Backups page, click Create Backup. In the displayed dialog box, enter a backup name and a description, and click OK. If you want to cancel the backup creation task, click Cancel.

                                      • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                      • The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
                                      • The time required for creating a manual backup depends on the data volume of the DB instance.
                                      +

                                    6. After a manual backup has been created, you can view and manage it on the Backups page.
                                    diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0069.html b/docs/gaussdb_mysql/umn/gaussdb_03_0069.html index b223413d7..af23b4926 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0069.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0069.html @@ -8,18 +8,18 @@

                                    Backup Space Calculation Methods

                                    There is a default backup chain (where there are seven backups). The first automated backup is a full backup, and subsequent automated backups are differential backups.

                                    In a backup chain, the backup space is released only after all full backups and differential backups are deleted.

                                    The billed space is calculated as follows:

                                    -
                                    • Logical space: Total size of the logical space – Logical size of the expired backup file
                                    • Physical space: Size of the first full backup file + Total size of subsequent differential backup files
                                    • Free space: There is free backup storage up to 100% of storage space.
                                    -

                                    Billed space = Min (Logical space, Physical space) – Free space = Min (Logical space, Physical space) – Storage space

                                    +
                                    • Logical space: Total size of the logical space – Logical size of the expired backup file
                                    • Physical space: Size of the first full backup file + Total size of subsequent differential backup files
                                    +

                                    Billed space = Min (Logical space, Physical space)

                                    Example

                                    A backup chain contains seven backups by default. There are 11 backups shown in the following figure. The 1st backup to the 7th belong to one backup chain and the 8th to the 11th belong to the other backup chain.

                                    Figure 1 Backup example

                                    -

                                    If there is 1,000 MB of backup space and the logical space is 1,000 MB each time, the physical space for the 1st backup is 1,000 MB. If the incremental data size is 100 MB each time, the physical space for the 2nd backup to 7th is 100 MB.

                                    +

                                    If the logical space is 1,000 MB each time, the physical space for the 1st backup is 1,000 MB. If the incremental data size is 100 MB each time, the physical space for the 2nd backup to 7th is 100 MB.

                                    A backup chain contains seven backups by default. The physical space for the 8th backup is 1,000 MB because it represents a new backup chain.

                                    Billed space includes the space of the two chains in the example.

                                    Suppose that after the 11th backup was created, and the 1st, 2nd and 3rd backups expired and were automatically deleted. The size of each space is calculated as follows:

                                    • Total size of the logical space for the 11th backup = 1,000 MB x 11 – 3,000 MB = 8,000 MB
                                    • Physical space: the amount of data backed up to OBS, that is, the sum of the physical space on the two chains.

                                      Physical space = 1,000 MB + 100 MB x 6 + 1,000 MB + 100 MB x 3 = 2,900 MB

                                      -
                                    • Total billed space = Min (8,000 MB, 2,900 MB) – 1,000 MB = 1,900 MB
                                    +
                                  6. Total billed space = Min (8,000 MB, 2,900 MB) = 2,900 MB
                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0082.html b/docs/gaussdb_mysql/umn/gaussdb_03_0082.html index 7959b9423..f5dc7e901 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 three types of the following: uppercase letters, lowercase letters, digits, and special characters.
                                  +
                                  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_0085.html b/docs/gaussdb_mysql/umn/gaussdb_03_0085.html index 486042952..c3464583e 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0085.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0085.html @@ -1,10 +1,10 @@

                                  Configuring Displayed Metrics

                                  -

                                  Function

                                  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 reported to Cloud Eye.

                                  +

                                  Function

                                  You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of metrics to be reported to Cloud Eye.

                                  -

                                  DB Instance Monitoring Metrics

                                  -
                                Table 1 GaussDB(for MySQL) operations recorded by CTS

                                Operation

                                Resource Type
                                Table 1 GaussDB(for MySQL) metrics

                                Metric ID

                                +

                                DB Instance Metrics

                                +
                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0087.html b/docs/gaussdb_mysql/umn/gaussdb_03_0087.html index 5281acfb0..2078e29a9 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0087.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0087.html @@ -1,10 +1,10 @@

                                Setting Alarm Rules

                                -

                                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.

                                +

                                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.

                                  +

                                  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.

                                Table 1 GaussDB(for MySQL) metrics

                                Metric ID

                                Metric
                                Table 1 Parameter description

                                Parameter

                                Parameter description

                                diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html index 2239b4753..c59c69ef8 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0088.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0088.html @@ -1,20 +1,20 @@

                                Viewing Monitoring Metrics

                                -

                                Scenarios

                                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 resource usage during database running, you can identify periods of high resource usage. You can also check error logs or slow query logs to optimize database performance.

                                +

                                Scenarios

                                The Cloud Eye service monitors operating statuses of DB instances. You can view the metrics of DB instances on the management console. By monitoring system resource usage during database running, you can identify periods of high resource usage. You can also check error logs or slow query logs to optimize database performance.

                                You can configure resource alarm rules on the Cloud Eye console. For details, see "Creating an Alarm Rule" in the Cloud Eye User Guide.

                                -

                                Prerequisites

                                • A DB instance is running properly.

                                  Monitoring metrics of the DB instances that are faulty or have been deleted cannot be displayed on the Cloud Eye console. You can view their monitoring metrics after they are rebooted or restored to be available.

                                  +

                                  Prerequisites

                                  • A DB instance is running properly.

                                    Metrics of the DB instances that are faulty or have been deleted cannot be displayed on the Cloud Eye console. You can view their metrics after they are rebooted or restored to normal.

                                  -

                                  If a DB instance has been faulty for 24 hours, Cloud Eye considers that it does not exist and deletes it from the monitoring object list. You need to manually clear the alarm rules created for the DB instance.

                                  +

                                  If a DB instance has been faulty for 24 hours, Cloud Eye considers it to no longer exist and deletes it from the monitoring object list. You need to manually clear the alarm rules created for the DB instance.

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

                                    +
                                    • A DB instance keeps running properly for about 10 minutes.

                                      For a newly created DB instance, you need to wait a bit before you can view the 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 Databases, click GaussDB(for MySQL).
                                  4. On the Instances page, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                    You can use either of the following methods to view monitoring metrics:

                                    -
                                    • Click the target DB instance. On the displayed Basic Information page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.
                                    • At the bottom part of the Basic Information page, locate the target read replica and click View Metric in the Operation column to go to the Cloud Eye console.
                                    -

                                  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.

                                    +

                                    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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances page, locate the target DB instance and click View Metrics in the Operation column to go to the Cloud Eye console.

                                      You can use either of the following methods to view metrics:

                                      +
                                      • Click the target DB instance. On the displayed Basic Information page, click View Metrics 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 Metrics in the Operation column to go to the Cloud Eye console.
                                      +

                                    5. On the Cloud Eye console, view DB instance 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 3131d0c73..9c093069a 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0092.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0092.html @@ -3,13 +3,13 @@

                                  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.
                                  +
                                  • Changing the vCPUs and memory 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 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 Databases, click GaussDB(for MySQL).
                                  4. You can change the instance specifications in either of the following ways:

                                    • On the Instances page, locate the target DB instance and choose More > Change Instance Specifications in the Operation column.
                                    • Click the target DB instance to go to the Basic Information page. In the DB Instance Information area, click Change in the Instance Specifications field.

                                  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 Instances page is Changing instance specifications. After a few minutes, you can click the instance name to view the new instance specifications on the displayed Basic Information page.

                                    -

                                    After the specifications of DB instances 8.0 are changed, the system will change the values of the following parameters accordingly: innodb_buffer_pool_size, innodb_log_buffer_size, max_connections, innodb_buffer_pool_instances, innodb_page_cleaners, innodb_parallel_read_threads, innodb_read_io_threads, innodb_write_io_threads, threadpool_size and query_cache_size.

                                    +

                                    After the specifications of DB instances 8.0 are changed, the system will change the values of the following parameters accordingly: innodb_buffer_pool_size, innodb_log_buffer_size, max_connections, innodb_buffer_pool_instances, innodb_page_cleaners, innodb_parallel_read_threads, innodb_read_io_threads, innodb_write_io_threads, threadpool_size and query_cache_size.

                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0110.html b/docs/gaussdb_mysql/umn/gaussdb_03_0110.html index b3014b6f3..cc46ca9a4 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0110.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0110.html @@ -1,10 +1,10 @@

                                  Introducing Read Replicas

                                  -

                                  Introduction

                                  Currently, DB instances support read replicas.

                                  +

                                  Introduction

                                  GaussDB(for MySQL) instances support read replicas.

                                  In read-intensive scenarios, a primary node may be unable to handle the read pressure and service performance may be affected. To offload read pressure on the primary node, you can create one or more read replicas in the same region as the primary node. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses for the primary node and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary node.

                                  -

                                  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.

                                    +

                                    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 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 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 dd1201fdc..389a0c437 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0111.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0111.html @@ -1,11 +1,11 @@ -

                                    Creating a Read Replica

                                    +

                                    Creating Read Replicas

                                    Scenarios

                                    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 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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances page, locate the target DB instance and choose More > Create Read Replica in the Operation column.

                                      Alternatively, click the target DB instance. In the DB Instance Topology area on the Basic Information page, click to create read replicas.

                                      +

                                      Procedure

                                      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 Databases, click GaussDB(for MySQL).
                                      4. On the Instances page, locate the instance that you want to create read replicas for and choose More > Create Read Replica in the Operation column.

                                        Alternatively, click the instance name to go to the Basic Information page. In the DB Instance Topology area, 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_0113.html b/docs/gaussdb_mysql/umn/gaussdb_03_0113.html index ab676fc62..59e8f0524 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0113.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0113.html @@ -1,17 +1,17 @@

                                    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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances 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.

                                        +

                                        A GaussDB(for MySQL) 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 Databases, click GaussDB(for MySQL).
                                        4. On the Instances page, click the instance name to go to the Basic Information page.
                                        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.

                                        -

                                        Automatic Failover

                                        GaussDB(for MySQL) uses an active-active high availability architecture and can automatically fail over to a new primary node that is automatically selected by the system.

                                        -

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

                                        +

                                        Automatic Failover

                                        GaussDB(for MySQL) uses a high availability active-active architecture that automatically fails over to a read replica automatically selected by the system.

                                        +

                                        Each read replica has a failover priority that determines which read replica is promoted if the primary node fails.

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

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

                                        +
                                        1. Read replicas available for promotion are identified.
                                        2. One or more read replicas with the highest priority are identified.
                                        3. One of the read replicas with the highest priority is selected and promoted. If the promotion fails due to network faults or abnormal replication status, GaussDB(for MySQL) attempts to promote another read replica by priority and repeats the process until a read replica is successfully promoted.
                                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0114.html b/docs/gaussdb_mysql/umn/gaussdb_03_0114.html index 99dfcaea7..4e0629fef 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0114.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0114.html @@ -5,10 +5,10 @@

                                        Deleted read replicas cannot be restored. Exercise caution when performing this operation.

                                        -

                                        Constraints

                                        • You can delete read replicas only when the DB instance has two or more than two read replicas. A GaussDB(for MySQL) DB instance must have at least one read replica.
                                        • DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are completed.
                                        +

                                        Constraints

                                        • You can only delete a read replica when the DB instance has two or more read replicas.
                                        • 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 Databases, click GaussDB(for MySQL).
                                        4. On the Instances 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 Instances 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 Databases, click GaussDB(for MySQL).
                                        4. On the Instances page, click the instance name.
                                        5. At the bottom of the Basic Information page, locate the read replica 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 Instances page later to check that the deletion is successful.
                                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0098.html b/docs/gaussdb_mysql/umn/gaussdb_05_0098.html index 91c6f6918..c319ed71c 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 Databases, click GaussDB(for MySQL).
                                        4. Choose Parameter Templates in the navigation pane on the left, locate the target parameter template, and click View Application Record in the Operation column on the Default Templates page or choose More > View Application Record on the Custom Templates page.

                                          You can view the name or ID of the DB instance to which the parameter template applies, as well as the application status, application time, and failure cause.

                                          +

                                          Procedure

                                          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 Databases, click GaussDB(for MySQL).
                                          4. Choose Parameter Templates in the navigation pane on the left, locate the target parameter template, and click View Application Record in the Operation column on the Default Templates page or choose More > View Application Record on the Custom Templates page.

                                            You can view the name or ID of the DB instance to which the parameter template applies, as well as the application status, application time, and failure cause.

                                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_0100.html b/docs/gaussdb_mysql/umn/gaussdb_05_0100.html index 82b165bb4..620a85b29 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_05_0100.html +++ b/docs/gaussdb_mysql/umn/gaussdb_05_0100.html @@ -1,9 +1,9 @@

                                        Modifying Database Remarks

                                        -

                                        Scenarios

                                        GaussDB(for MySQL) allows you to modify remarks of created databases.

                                        +

                                        Scenarios

                                        GaussDB(for MySQL) allows you to modify remarks of created databases.

                                        -

                                        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 Databases, click GaussDB(for MySQL).
                                        4. On the Instances page, click the target DB instance.
                                        5. In the navigation pane, choose Databases.
                                        6. Locate the target database and click in the Remarks column.

                                          The database remarks can be empty or contain up to 512 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 Databases, click GaussDB(for MySQL).
                                          4. On the Instances page, click the instance name.
                                          5. In the navigation pane, choose Databases.
                                          6. Locate the target database and click in the Remarks column.

                                            The database remarks can be empty or contain up to 512 characters.

                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_05_2265.html b/docs/gaussdb_mysql/umn/gaussdb_05_2265.html index 51ba95eab..c3487c602 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_05_2265.html +++ b/docs/gaussdb_mysql/umn/gaussdb_05_2265.html @@ -1,9 +1,9 @@

                                          Upgrading the Minor Version of a DB Instance

                                          -

                                          Scenarios

                                          GaussDB(for MySQL) supports manual minor version upgrades, which can improve performance, add new functions, and fix bugs.

                                          +

                                          Scenarios

                                          You can manually upgrade minor versions of your instances to 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.
                                          +

                                          Precautions

                                          • The upgrade will cause the instance to reboot and interrupt services intermittently. 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 Service List. Under Databases, click GaussDB(for MySQL).
                                          4. On the Instances page, click the target instance 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.

                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_08_0112.html b/docs/gaussdb_mysql/umn/gaussdb_08_0112.html index 8c908ab65..0567cf34a 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_08_0112.html +++ b/docs/gaussdb_mysql/umn/gaussdb_08_0112.html @@ -1,7 +1,7 @@

                                          Modifying a Parameter Template

                                          -

                                          You can modify parameters in a custom parameter template to optimize GaussDB(for MySQL) database performance.

                                          +

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

                                          @@ -16,13 +16,13 @@

                                        -

                                        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 Databases, click GaussDB(for MySQL).
                                        4. On the Instances 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:

                                          +

                                          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 Databases, click GaussDB(for MySQL).
                                          4. On the Instances page, click the instance name.
                                          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 Instances page is Pending reboot, you must reboot the DB instance for the modifications of this parameter to take effect.
                                            • If the value is No, the modification of this parameter takes effect immediately.
                                            -
                                            • To save the modifications, click Save.
                                            • To cancel the modifications, click Cancel.
                                            • To preview the modifications, click Preview.
                                            +
                                            • To save the modifications, click Save.
                                            • To cancel the modifications, click Cancel.
                                            • To preview the modifications, click Preview.

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

                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html index c039c2494..400e18abc 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_11_0017.html +++ b/docs/gaussdb_mysql/umn/gaussdb_11_0017.html @@ -2,7 +2,7 @@

                                          Creating a Proxy Instance

                                          A proxy instance enables read and write requests to be automatically routed through its IP address. This section describes how to create a proxy instance.

                                          -

                                          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 Databases, click GaussDB(for MySQL).
                                          4. On the Instances page, click the target DB instance.
                                          5. In the navigation pane on the left, choose Database Proxy.
                                          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.
                                                +

                                                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 Databases, click GaussDB(for MySQL).
                                                4. On the Instances page, click the instance name.
                                                5. In the navigation pane on the left, choose Database Proxy.
                                                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.
                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq.html b/docs/gaussdb_mysql/umn/gaussdb_faq.html index 9deb3b9fc..4503277e2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq.html @@ -4,7 +4,7 @@
                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0002.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0002.html index 20c885514..2ea4716f2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0002.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0002.html @@ -1,7 +1,7 @@ -

                                                  Does GaussDB(for MySQL) Support Compute and Storage Decoupling?

                                                  -

                                                  GaussDB(for MySQL) supports the decoupling of compute and storage, improving your experience in terms of high availability, backup and restoration, upgrade and capacity expansion.

                                                  +

                                                  Does GaussDB(for MySQL) Support Decoupled Storage and Compute?

                                                  +

                                                  Yes. GaussDB(for MySQL) decouples storage from compute, which improves user experience in terms of high availability, backup and restoration, and upgrade and scale-out.

                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0003.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0003.html index 1e4584f69..ca45370fd 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0003.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0003.html @@ -1,7 +1,7 @@ -

                                                  What's the Maximum Data Volume Supported by GaussDB(for MySQL)?

                                                  -

                                                  GaussDB(for MySQL) supports up to 128 TB of data and can easily handle large amounts of data requests.

                                                  +

                                                  What's the Maximum Data Volume Supported by GaussDB(for MySQL)?

                                                  +

                                                  GaussDB(for MySQL) can store up to 128 TB of data.

                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0005.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0005.html index dbca00bc9..9cfc8727f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0005.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0005.html @@ -1,7 +1,7 @@ -

                                                  Does GaussDB(for MySQL) Support Automatic Failover?

                                                  -

                                                  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 automatically fails over to a read replica with the highest priority and the original primary node is restored in the background.

                                                  +

                                                  Does GaussDB(for MySQL) Support Automatic Failover?

                                                  +

                                                  During the creation of a GaussDB(for MySQL) instance, a primary node and a read replica are both created. If the primary node fails, the system automatically fails over to a read replica with the highest priority and the original primary node is restored in the background.

                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0006.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0006.html index 5aab8fe37..814529028 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0006.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0006.html @@ -1,6 +1,6 @@ -

                                                  What Should I Do When Modifications to GaussDB(for MySQL) Instance Parameters Does Not Take Effect?

                                                  +

                                                  What Should I Do When Modifications to GaussDB(for MySQL) Instance Parameters Does Not Take Effect?

                                                  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 template on the management console. The modifications to dynamic parameters take effect immediately. The modifications to static parameters take effect only after you reboot the DB instance associated with the parameter template.

                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0007.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0007.html index fafd81a73..a8a1b4c32 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0007.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0007.html @@ -1,7 +1,7 @@ -

                                                  How Many Read Replicas Can I Create for a GaussDB(for MySQL) DB Instance?

                                                  -

                                                  You can create a maximum of 15 read replicas for a GaussDB(for MySQL) DB instance.

                                                  +

                                                  How Many Read Replicas Can I Create for a GaussDB(for MySQL) Instance?

                                                  +

                                                  You can create a maximum of 15 read replicas for a GaussDB(for MySQL) instance.

                                                  diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0009.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0009.html index fb3d5ab0f..482272b35 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0009.html @@ -1,8 +1,8 @@ -

                                                  What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) DB Instance?

                                                  +

                                                  What Should I Do If an ECS Cannot Connect to a GaussDB(for MySQL) Instance?

                                                  Perform the following steps to identify the problem:

                                                  -
                                                  1. Check whether the ECS and GaussDB(for MySQL) DB instance are located in the same VPC.

                                                    • 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 located.
                                                    +
                                                    1. Check whether the ECS and DB instance are located in the same VPC.

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

                                                    2. Check whether a security group has been created for the ECS.

                                                      • If a security group has been created, check whether its configuration rules are suitable.

                                                        For details, see security group description in Step 1: Create a DB Instance. Then, go to 3.

                                                      • If no security group has been created, go to the VPC console from the ECS details page and create a security group.

                                                    3. Check whether the ECS can connect to the DB instance over the instance port.

                                                      The default port of the DB instance is 3306.

                                                      diff --git a/docs/gaussdb_mysql/umn/gaussdb_faq_0010.html b/docs/gaussdb_mysql/umn/gaussdb_faq_0010.html index 2cf96a283..79ad5bb0f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_faq_0010.html +++ b/docs/gaussdb_mysql/umn/gaussdb_faq_0010.html @@ -1,11 +1,11 @@ -

                                                      How Can I Import the Root Certificate to a Windows or Linux OS?

                                                      -

                                                      Importing the Root Certificate to the Windows OS

                                                      1. Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.
                                                      2. On the displayed console, choose File > Add/Remove Snap-in.
                                                      3. In the left Available snap-ins pane of the displayed Add or Remove Snap-ins dialog box, select Certificates and click Add.
                                                      4. In the displayed Certificates snap-in dialog box, select Computer account and click Next.
                                                      5. In the displayed Select Computer dialog box, click Finish.
                                                      6. In the Add or Remove Snap-ins dialog box, click OK.
                                                      7. On the console, double-click Certificates.
                                                      8. Right-click Trusted Root Certification Authorities and choose All Tasks > Import.
                                                      9. In the displayed Certificate Import Wizard dialog box, click Next.
                                                      10. Click Browse to change the file type to All Files (*.*).
                                                      11. Locate the downloaded root certificate ca.pem file and click Open. Then, click Next.

                                                        You must change the file type to All Files (*.*) because .pem is not a standard certificate extension name.

                                                        +

                                                        How Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?

                                                        +

                                                        Importing the Certificate to a Windows Server

                                                        1. Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.
                                                        2. On the displayed console, choose File > Add/Remove Snap-in.
                                                        3. In the left Available snap-ins pane of the displayed Add or Remove Snap-ins dialog box, select Certificates and click Add.
                                                        4. In the displayed Certificates snap-in dialog box, select Computer account and click Next.
                                                        5. In the displayed Select Computer dialog box, click Finish.
                                                        6. In the Add or Remove Snap-ins dialog box, click OK.
                                                        7. On the console, double-click Certificates.
                                                        8. Right-click Trusted Root Certification Authorities and choose All Tasks > Import.
                                                        9. In the displayed Certificate Import Wizard dialog box, click Next.
                                                        10. Click Browse to change the file type to All Files (*.*).
                                                        11. Locate the downloaded root certificate ca.pem file and click Open. Then, click Next.

                                                          You must change the file type to All Files (*.*) because .pem is not a standard certificate extension name.

                                                        12. Click Next.
                                                        13. Click Finish.
                                                        14. Click OK to complete the import of the root certificate.
                                                        -

                                                        Importing the Root Certificate to the Linux OS

                                                        You can use a connection tool (such as WinSCP or PuTTY) to upload the certificate to any directory on a Linux OS.

                                                        +

                                                        Importing the Certificate to a Linux Server

                                                        You can use a connection tool (such as WinSCP or PuTTY) to upload the certificate to any directory on a Linux server.

                                                        Example:

                                                        Figure 1 Importing a certificate
                                                        diff --git a/docs/gaussdb_mysql/umn/gaussdb_task_0002.html b/docs/gaussdb_mysql/umn/gaussdb_task_0002.html index de984c114..cca62824d 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_task_0002.html +++ b/docs/gaussdb_mysql/umn/gaussdb_task_0002.html @@ -4,7 +4,7 @@

                                                        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 Databases, click GaussDB(for MySQL).
                                                        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:

                                                          +

                                                          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 Databases, click GaussDB(for MySQL).
                                                          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 the records of instant tasks in any of the following statuses:

                                                            • Running
                                                            • Completed
                                                            • Failed

                                                          diff --git a/docs/gaussdb_mysql/umn/gaussdb_usermanual.html b/docs/gaussdb_mysql/umn/gaussdb_usermanual.html index 5156959ff..c5a663fb3 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_usermanual.html +++ b/docs/gaussdb_mysql/umn/gaussdb_usermanual.html @@ -1,6 +1,6 @@ -

                                                          Working with GaussDB(for MySQL)

                                                          +

                                                          Working with GaussDB(for MySQL)

                                                            diff --git a/docs/gaussdb_mysql/umn/gaussdbformysql_03_0131.html b/docs/gaussdb_mysql/umn/gaussdbformysql_03_0131.html index 15a95e0ab..eaa49487e 100644 --- a/docs/gaussdb_mysql/umn/gaussdbformysql_03_0131.html +++ b/docs/gaussdb_mysql/umn/gaussdbformysql_03_0131.html @@ -35,7 +35,7 @@

                                The password must:

                                • Consist of 8 to 32 characters.
                                • Contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and the following special characters: ~!@#$%^*-_=+?,()&|.
                                • Comply with the values of validate_password parameters.

                                  To check the password-related parameter values, click a DB instance name, choose Parameters in the navigation pane, and search for validate_password in the upper right corner of the page.

                                -
                                • Cannot be the username or the username spelled backwards.
                                +
                                • Be different from the username or the username spelled backwards.

                                Confirm Password

                                diff --git a/docs/gaussdb_mysql/umn/gaussdbformysql_03_0133.html b/docs/gaussdb_mysql/umn/gaussdbformysql_03_0133.html index 549df77a7..3c2e33156 100644 --- a/docs/gaussdb_mysql/umn/gaussdbformysql_03_0133.html +++ b/docs/gaussdb_mysql/umn/gaussdbformysql_03_0133.html @@ -5,10 +5,10 @@

                                Constraints

                                This operation is not allowed when another operation is being performed on your 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 Databases, click GaussDB(for MySQL).
                                4. On the Instances page, click the target DB instance.
                                5. In the navigation pane, choose Accounts. On the displayed page, locate the target username and click Reset Password in the Operation column.
                                6. In the displayed dialog box, enter a new password and confirm the password.

                                  The password must:

                                  -
                                  • Consist of 8 to 32 characters.
                                  • Contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and the following special characters: ~!@#$%^*-_=+?,()&|.
                                  • Comply with the values of validate_password parameters.

                                    To check the parameter values, click a DB instance name, choose Parameters in the navigation pane, and search for validate_password 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 Databases, click GaussDB(for MySQL).
                                    4. On the Instances page, click the target DB instance.
                                    5. In the navigation pane, choose Accounts. On the displayed page, locate the target username and click Reset Password in the Operation column.
                                    6. In the displayed dialog box, enter a new password and confirm it.

                                      The password must meet the following requirements:

                                      +
                                      • It must consist of 8 to 32 characters.
                                      • It must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters ~!@#$%^*-_=+?,()&|.
                                      • It must comply with the values of validate_password parameters.

                                        To check the parameter values, click a DB instance name, choose Parameters in the navigation pane, and search for validate_password in the upper right corner of the page.

                                      -
                                      • Be the same as that you entered in the Password text box.
                                      • Cannot be the username or the username spelled backwards.
                                      +
                                      • The password you entered in the Confirm Password text box must be the same as that you entered in the New Password text box.
                                      • It cannot be the username or the username spelled backwards.

                                    7. Click OK.
                                diff --git a/docs/gaussdb_mysql/umn/introduction.html b/docs/gaussdb_mysql/umn/introduction.html index f61ead2e7..014921579 100644 --- a/docs/gaussdb_mysql/umn/introduction.html +++ b/docs/gaussdb_mysql/umn/introduction.html @@ -2,8 +2,8 @@

                                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.

                                -

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

                                +

                                A GaussDB(for MySQL) 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).

                                diff --git a/docs/gaussdb_mysql/umn/quick_start.html b/docs/gaussdb_mysql/umn/quick_start.html index dc5c079e1..76e39abe3 100644 --- a/docs/gaussdb_mysql/umn/quick_start.html +++ b/docs/gaussdb_mysql/umn/quick_start.html @@ -1,7 +1,7 @@

                                Connecting to a DB Instance

                                -

                                You can connect a DB instance over a private or a public network.

                                +

                                You can connect a DB instance over a private or public network.

                                @@ -18,7 +18,7 @@ @@ -27,20 +27,20 @@ - -
                                Table 1 Connection methods

                                Connect Through

                                Private IP address

                                The system provides a private IP address by default.

                                -

                                When your applications are deployed on an ECS that is in the same region and VPC as the GaussDB(for MySQL) DB instance, you are advised to connect to the DB instance through the ECS over a private IP address.

                                +

                                When your applications are deployed on an ECS that is in the same region and VPC as the DB instance, you are advised to connect to the DB instance through the ECS over a private IP address.
                                • Secure and excellent performance
                                • Recommended

                                EIP

                                If you cannot access the GaussDB(for MySQL) DB instance over a private IP address, bind an EIP to the DB instance and connect it to an ECS (or a public network host) over the EIP.

                                +

                                If you cannot access a DB instance over a private IP address, bind an EIP to the DB instance and connect it to an ECS (or a public network host) over the EIP.

                                • A relatively Low lower level of security compared to the other two connection modes.
                                • To achieve a higher data transmission rate and security level, you are advised to migrate your applications to an ECS that is in the same VPC as your GaussDB(for MySQL) DB instance and use a private IP address to access the DB instance.
                                +
                                • A relatively Low lower level of security compared to the other two connection modes.
                                • To achieve a higher data transmission rate and security level, you are advised to migrate your applications to an ECS that is in the same VPC as your DB instance and use a private IP address to access the DB instance.
                                -
                                • VPC: indicates the Virtual Private Cloud.
                                • ECS: indicates the Elastic Cloud Server.
                                • If the ECS is in the same VPC as the GaussDB(for MySQL) DB instance, you do not need to apply for an EIP.
                                +
                                • VPC: indicates the Virtual Private Cloud.
                                • ECS: indicates the Elastic Cloud Server.
                                • If the ECS is in the same VPC as the DB instance, you do not need to apply for an EIP.