From 25e3252651e64fde894073df0951bbafca607c99 Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Thu, 16 Nov 2023 08:35:02 +0000 Subject: [PATCH] Update content --- umn/source/change_history.rst | 88 ++++++++++--------- .../step_1_create_a_db_instance.rst | 6 +- .../step_2_configure_security_group_rules.rst | 2 +- .../step_1_create_a_db_instance.rst | 6 +- .../step_2_bind_an_eip.rst | 2 +- .../creating_a_manual_backup.rst | 10 +-- .../deleting_a_manual_backup.rst | 2 +- .../restoring_data_from_a_backup.rst | 2 +- .../binding_and_unbinding_an_eip.rst | 2 +- .../changing_a_database_port.rst | 2 +- .../changing_a_security_group.rst | 2 +- .../resetting_the_administrator_password.rst | 4 +- .../assigning_read_weights.rst | 4 +- .../disabling_read_write_splitting.rst | 2 +- .../enabling_read_write_splitting.rst | 2 +- .../changing_a_db_instance_name.rst | 12 +-- ...anging_vcpus_and_memory_of_an_instance.rst | 4 +- .../deleting_a_db_instance.rst | 6 +- .../exporting_db_instance_information.rst | 4 +- .../rebooting_a_db_instance.rst | 2 +- .../key_operations_supported_by_cts.rst | 2 + .../logs/viewing_error_logs.rst | 2 +- .../logs/viewing_slow_query_logs.rst | 2 +- .../monitoring/viewing_monitoring_metrics.rst | 2 +- .../applying_a_parameter_template.rst | 2 +- .../comparing_a_parameter_template.rst | 4 +- .../creating_a_parameter_template.rst | 2 +- .../deleting_a_parameter_template.rst | 2 +- .../exporting_parameters.rst | 2 +- .../modifying_a_parameter_template.rst | 6 +- ...fying_a_parameter_template_description.rst | 2 +- .../replicating_a_parameter_template.rst | 6 +- .../resetting_a_parameter_template.rst | 2 +- ...cation_records_of_a_parameter_template.rst | 2 +- .../viewing_parameter_change_history.rst | 4 +- .../read_replicas/creating_a_read_replica.rst | 2 +- .../read_replicas/deleting_a_read_replica.rst | 6 +- ...ing_a_read_replica_to_the_primary_node.rst | 2 +- 38 files changed, 110 insertions(+), 106 deletions(-) diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index fd116a3..782056a 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -5,44 +5,50 @@ Change History ============== -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| Released On | Description | -+===================================+================================================================================================+ -| 2023-10-25 | Modified the following content: | -| | | -| | Added specifications (2 vCPUs \| 8 GB) in :ref:`DB Instance Specifications `. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2023-04-06 | Added :ref:`Changing an Instance Description `. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2022-11-30 | Modified the following content: | -| | | -| | - Added :ref:`Introducing Read/Write Splitting `. | -| | - Added :ref:`Enabling Read/Write Splitting `. | -| | - Added :ref:`Changing the Read/Write Splitting Address `. | -| | - Added :ref:`Disabling Read/Write Splitting `. | -| | - Added :ref:`Enabling or Disabling Access Control `. | -| | - Added :ref:`Enabling or Disabling Access Control `. | -| | - Added :ref:`Testing Read/Write Splitting Performance `. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2021-12-09 | Modified the following content: | -| | | -| | - Modified instance specifications. | -| | - Modified the parameter description about adding a security group rule. | -| | - Modified the description of changing parameters in parameter templates. | -| | - Modified the content of the section "Task Center". | -| | - Optimized the description of the section "Viewing Monitoring Metrics". | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2021-11-30 | Optimized :ref:`Deleting a Task Record `. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2021-08-31 | Added :ref:`Enabling or Disabling SQL Explorer `. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2020-10-31 | Optimized the content in :ref:`Configuring Displayed Metrics `. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2020-07-31 | Modified the following content: | -| | | -| | - Product description in :ref:`What Is GaussDB(for MySQL)? ` | -| | | -| | - Optimized DB instance specifications. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ -| 2020-07-14 | This issue is the first official release. | -+-----------------------------------+------------------------------------------------------------------------------------------------+ ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| Released On | Description | ++===================================+============================================================================================================================================+ +| 2023-11-13 | Modified the following content: | +| | | +| | Allowed you to change the node names synchronously during DB instance name change in :ref:`Changing a DB Instance Name `. | +| | | +| | Added the event of deleting a task from the task center in :ref:`Key Operations Supported by CTS `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-10-25 | Modified the following content: | +| | | +| | Added specifications (2 vCPUs \| 8 GB) in :ref:`DB Instance Specifications `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-04-06 | Added :ref:`Changing an Instance Description `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-11-30 | Modified the following content: | +| | | +| | - Added :ref:`Introducing Read/Write Splitting `. | +| | - Added :ref:`Enabling Read/Write Splitting `. | +| | - Added :ref:`Changing the Read/Write Splitting Address `. | +| | - Added :ref:`Disabling Read/Write Splitting `. | +| | - Added :ref:`Enabling or Disabling Access Control `. | +| | - Added :ref:`Enabling or Disabling Access Control `. | +| | - Added :ref:`Testing Read/Write Splitting Performance `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-12-09 | Modified the following content: | +| | | +| | - Modified instance specifications. | +| | - Modified the parameter description about adding a security group rule. | +| | - Modified the description of changing parameters in parameter templates. | +| | - Modified the content of the section "Task Center". | +| | - Optimized the description of the section "Viewing Monitoring Metrics". | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-11-30 | Optimized :ref:`Deleting a Task Record `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-08-31 | Added :ref:`Enabling or Disabling SQL Explorer `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-10-31 | Optimized the content in :ref:`Configuring Displayed Metrics `. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-07-31 | Modified the following content: | +| | | +| | - Product description in :ref:`What Is GaussDB(for MySQL)? ` | +| | | +| | - Optimized DB instance specifications. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-07-14 | This issue is the first official release. | ++-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_1_create_a_db_instance.rst b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_1_create_a_db_instance.rst index acfeca1..6293e54 100644 --- a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_1_create_a_db_instance.rst +++ b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_1_create_a_db_instance.rst @@ -16,7 +16,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click **Create DB Instance**. +#. On the **Instances** page, click **Create DB Instance**. #. On the displayed page, configure parameters about the DB instance specifications. Then, click **Create Now**. .. table:: **Table 1** Basic information @@ -24,7 +24,7 @@ Procedure +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Parameter | Description | +===================================+====================================================================================================================================================================================================================================================+ - | Region | A region where the tenant is located. You can change it on the creation page, or go back to the **Instance Management** page and change it in the upper left corner. | + | Region | A region where the tenant is located. You can change it on the creation page, or go back to the **Instances** page and change it in the upper left corner. | | | | | | .. important:: | | | | @@ -118,7 +118,7 @@ Procedure - If you need to modify your settings, click **Previous**. - If you do not need to modify your settings, click **Submit**. -#. To view and manage DB instances, go to the **Instance Management** page. +#. To view and manage DB instances, go to the **Instances** page. - During the creation process, the DB instance status is **Creating**. When the status of the created instance is **Available**, the DB instance can be used. diff --git a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_2_configure_security_group_rules.rst b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_2_configure_security_group_rules.rst index d6c8e74..72c3013 100644 --- a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_2_configure_security_group_rules.rst +++ b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_2_configure_security_group_rules.rst @@ -42,7 +42,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. Configure security group rules. diff --git a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_1_create_a_db_instance.rst b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_1_create_a_db_instance.rst index 4a310de..b5a76ed 100644 --- a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_1_create_a_db_instance.rst +++ b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_1_create_a_db_instance.rst @@ -16,7 +16,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click **Create DB Instance**. +#. On the **Instances** page, click **Create DB Instance**. #. On the displayed page, configure parameters about the DB instance specifications. Then, click **Create Now**. .. table:: **Table 1** Basic information @@ -24,7 +24,7 @@ Procedure +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Parameter | Description | +===================================+====================================================================================================================================================================================================================================================+ - | Region | A region where the tenant is located. You can change it on the creation page, or go back to the **Instance Management** page and change it in the upper left corner. | + | Region | A region where the tenant is located. You can change it on the creation page, or go back to the **Instances** page and change it in the upper left corner. | | | | | | .. important:: | | | | @@ -118,7 +118,7 @@ Procedure - If you need to modify your settings, click **Previous**. - If you do not need to modify your settings, click **Submit**. -#. To view and manage DB instances, go to the **Instance Management** page. +#. To view and manage DB instances, go to the **Instances** page. - During the creation process, the DB instance status is **Creating**. When the status of the created instance is **Available**, the DB instance can be used. diff --git a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_2_bind_an_eip.rst b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_2_bind_an_eip.rst index 2f49352..7549ed2 100644 --- a/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_2_bind_an_eip.rst +++ b/umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_2_bind_an_eip.rst @@ -24,7 +24,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. In the **Network Information** area, click **Bind** in the Private IP Address field. diff --git a/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/creating_a_manual_backup.rst b/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/creating_a_manual_backup.rst index 20625bd..f466b93 100644 --- a/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/creating_a_manual_backup.rst +++ b/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/creating_a_manual_backup.rst @@ -18,14 +18,14 @@ Method 1 #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, locate the target DB instance and choose **More** > **Create Backup** in the **Operation** column. +#. On the **Instances** page, locate the target DB instance and choose **More** > **Create Backup** in the **Operation** column. #. In the displayed dialog box, enter a backup name and description. Then, click **OK**. If you want to cancel the backup creation task, click **Cancel**. - The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). - The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>& - The time required for creating a manual backup depends on the data volume of the DB instance. -#. After a manual backup has been created, you can view and manage it on the **Backup Management** page. +#. After a manual backup has been created, you can view and manage it on the **Backups** page. Method 2 -------- @@ -33,14 +33,14 @@ Method 2 #. Log in to the management console. #. Click |image2| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. -#. On the **Backups & Restorations** page, click **Create Backup**. In the displayed dialog box, enter a backup name and a description, and click **OK**. If you want to cancel the backup creation task, click **Cancel**. +#. On the **Instances** page, click the target DB instance. +#. On the **Backups** page, click **Create Backup**. In the displayed dialog box, enter a backup name and a description, and click **OK**. If you want to cancel the backup creation task, click **Cancel**. - The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). - The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>& - The time required for creating a manual backup depends on the data volume of the DB instance. -#. After a manual backup has been created, you can view and manage it on the **Backup Management** page. +#. After a manual backup has been created, you can view and manage it on the **Backups** page. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png .. |image2| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/deleting_a_manual_backup.rst b/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/deleting_a_manual_backup.rst index 94b27fb..4f9bb95 100644 --- a/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/deleting_a_manual_backup.rst +++ b/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/deleting_a_manual_backup.rst @@ -23,7 +23,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. In the navigation pane on the left, choose **Backup Management**. On the displayed page, locate the manual backup to be deleted and click **Delete** in the **Operation** column. +#. In the navigation pane on the left, choose **Backups**. On the displayed page, locate the manual backup to be deleted and click **Delete** in the **Operation** column. The following backups cannot be deleted: diff --git a/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/restoring_data_from_a_backup.rst b/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/restoring_data_from_a_backup.rst index f943762..4121227 100644 --- a/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/restoring_data_from_a_backup.rst +++ b/umn/source/working_with_gaussdbfor_mysql/backups_and_restorations/restoring_data_from_a_backup.rst @@ -19,7 +19,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Backup Management** page, select the backup to be restored and click **Restore** in the **Operation** column. +#. On the **Backups** page, select the backup to be restored and click **Restore** in the **Operation** column. #. Click **OK**. Currently, you can only restore data to a new DB instance. diff --git a/umn/source/working_with_gaussdbfor_mysql/connection_management/binding_and_unbinding_an_eip.rst b/umn/source/working_with_gaussdbfor_mysql/connection_management/binding_and_unbinding_an_eip.rst index c7698a2..630aad0 100644 --- a/umn/source/working_with_gaussdbfor_mysql/connection_management/binding_and_unbinding_an_eip.rst +++ b/umn/source/working_with_gaussdbfor_mysql/connection_management/binding_and_unbinding_an_eip.rst @@ -31,7 +31,7 @@ Binding an EIP #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the **Network Information** area, click **Bind** in the **Public IP Address (EIP)** field. diff --git a/umn/source/working_with_gaussdbfor_mysql/connection_management/changing_a_database_port.rst b/umn/source/working_with_gaussdbfor_mysql/connection_management/changing_a_database_port.rst index a5dea2b..40649ff 100644 --- a/umn/source/working_with_gaussdbfor_mysql/connection_management/changing_a_database_port.rst +++ b/umn/source/working_with_gaussdbfor_mysql/connection_management/changing_a_database_port.rst @@ -24,7 +24,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the **Network Information** area, click |image2| in the **Database Port** field. diff --git a/umn/source/working_with_gaussdbfor_mysql/data_security/changing_a_security_group.rst b/umn/source/working_with_gaussdbfor_mysql/data_security/changing_a_security_group.rst index 40d245e..13cc2ae 100644 --- a/umn/source/working_with_gaussdbfor_mysql/data_security/changing_a_security_group.rst +++ b/umn/source/working_with_gaussdbfor_mysql/data_security/changing_a_security_group.rst @@ -16,7 +16,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the **Network Information** area, click |image2| in the **Security Group** field. - To submit the change, click |image3|. diff --git a/umn/source/working_with_gaussdbfor_mysql/data_security/resetting_the_administrator_password.rst b/umn/source/working_with_gaussdbfor_mysql/data_security/resetting_the_administrator_password.rst index d321311..ddcae50 100644 --- a/umn/source/working_with_gaussdbfor_mysql/data_security/resetting_the_administrator_password.rst +++ b/umn/source/working_with_gaussdbfor_mysql/data_security/resetting_the_administrator_password.rst @@ -33,7 +33,7 @@ Method 1 #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, locate the target DB instance and choose **More** > **Reset Password** in the **Operation** column. +#. On the **Instances** page, locate the target DB instance and choose **More** > **Reset Password** in the **Operation** column. #. Enter a new password and confirm the password. @@ -55,7 +55,7 @@ Method 2 #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the **DB Instance Information** area, click **Reset Password** in the **Administrator** field. In the displayed dialog box, enter a new password and confirm the password. diff --git a/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/assigning_read_weights.rst b/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/assigning_read_weights.rst index 5afccc5..e4a0e20 100644 --- a/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/assigning_read_weights.rst +++ b/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/assigning_read_weights.rst @@ -12,7 +12,7 @@ Description - After read/write splitting is enabled, you can assign read weights for the primary node and read replicas. - The default read weight of the primary node is 0. The higher read weight the primary node is assigned, the more read requests it can process. -- If the read weight of a read replica is 0, the read replica does not process any read requests. +- When the read weights of all nodes are 0, services are not affected. In this case, the primary node processes all read and write requests by default. - The weight of a read replica ranges from 0 to 1000. - For details about how to assign read weights, see :ref:`Weight Assignment Rules `. @@ -42,7 +42,7 @@ Procedure #. Under **Database**, click **GaussDB**. In the navigation pane on the left, click **GaussDB(for MySQL)**. -#. On the **Instance Management** page, click the instance name to go to the **Basic Information** page. +#. On the **Instances** page, click the instance name to go to the **Basic Information** page. #. In the navigation pane on the left, choose **Database Proxy**. On the displayed page, click the **Read/Write Splitting** tab. diff --git a/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/disabling_read_write_splitting.rst b/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/disabling_read_write_splitting.rst index 266f9bc..1e22ca7 100644 --- a/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/disabling_read_write_splitting.rst +++ b/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/disabling_read_write_splitting.rst @@ -13,7 +13,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the navigation pane on the left, choose **Database Proxy**. #. On the **Database Proxy** page, locate the desired proxy instance and click **Disable Database Proxy** in the **Operation** column. In the displayed dialog box, click **Yes**. diff --git a/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/enabling_read_write_splitting.rst b/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/enabling_read_write_splitting.rst index e4d087c..e003200 100644 --- a/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/enabling_read_write_splitting.rst +++ b/umn/source/working_with_gaussdbfor_mysql/database_proxy_read_write_splitting/enabling_read_write_splitting.rst @@ -16,7 +16,7 @@ Procedure #. Under **Database**, click **GaussDB**. In the navigation pane on the left, click **GaussDB(for MySQL)**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the navigation pane on the left, choose **Database Proxy**. diff --git a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_a_db_instance_name.rst b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_a_db_instance_name.rst index 3df5610..21982ee 100644 --- a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_a_db_instance_name.rst +++ b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_a_db_instance_name.rst @@ -14,17 +14,13 @@ Procedure --------- #. Log in to the management console. - #. Click |image1| in the upper left corner and select a region and a project. - #. Click **Service List**. Under **Database**, click **GaussDB**. +#. On the **Instances** page, locate the instance name and click |image2| in the **Name/ID** column to edit the instance name. -#. On the **Instance Management** page, locate the target DB instance and click |image2| next to it to edit the DB instance name. Then, click **OK**. - - The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed. - - - To submit the change, click **OK**. - - To cancel the change, click **Cancel**. + - The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed. + - When changing the instance name, you can determine whether to select **Change node names synchronously** as required. If this option is selected, the names of the corresponding nodes are changed when the instance name is changed. If this option is not selected, only the instance name is changed, and the corresponding node names are not changed. + - If you want to submit the change, click **OK**. If you want to cancel the change, click **Cancel**. #. View the result of the change on the **Basic Information** page. diff --git a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_vcpus_and_memory_of_an_instance.rst b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_vcpus_and_memory_of_an_instance.rst index efadcd2..fe3fd50 100644 --- a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_vcpus_and_memory_of_an_instance.rst +++ b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/changing_vcpus_and_memory_of_an_instance.rst @@ -29,7 +29,7 @@ Procedure #. You can change the instance specifications in either of the following ways: - - On the **Instance Management** page, locate the target DB instance and choose **More** > **Change Instance Specifications** in the **Operation** column. + - On the **Instances** page, locate the target DB instance and choose **More** > **Change Instance Specifications** in the **Operation** column. - Click the target DB instance to go to the **Basic Information** page. In the **DB Instance Information** area, click **Change** in the **Instance Specifications** field. #. On the displayed page, specify the new instance specifications, and click **Next**. @@ -41,7 +41,7 @@ Procedure #. View the DB instance specification change result. - Changing the instance specifications takes 5-15 minutes. During this period, the status of the instance on the **Instance Management** page is **Changing instance specifications**. After a few minutes, you can click the instance name to view the new instance specifications on the displayed **Basic Information** page. + 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. .. important:: diff --git a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/deleting_a_db_instance.rst b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/deleting_a_db_instance.rst index 98b9ff0..cbb35c2 100644 --- a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/deleting_a_db_instance.rst +++ b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/deleting_a_db_instance.rst @@ -8,7 +8,7 @@ Deleting a DB Instance Scenarios --------- -You can manually delete a DB instance on the **Instance Management** page. +You can manually delete a DB instance on the **Instances** page. .. important:: @@ -27,7 +27,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, locate the DB instance to be deleted and click **More** > **Delete** in the **Operation** column. -#. In the displayed dialog box, click **Yes**. Refresh the **Instance Management** page later to check that the deletion is successful. +#. On the **Instances** page, locate the DB instance to be deleted and click **More** > **Delete** in the **Operation** column. +#. In the displayed dialog box, click **Yes**. Refresh the **Instances** page later to check that the deletion is successful. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/exporting_db_instance_information.rst b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/exporting_db_instance_information.rst index 6e5a281..d148a18 100644 --- a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/exporting_db_instance_information.rst +++ b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/exporting_db_instance_information.rst @@ -16,7 +16,7 @@ Exporting Information About All DB Instances #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click |image2| in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click **Export**. +#. On the **Instances** page, click |image2| in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click **Export**. #. After the export task is complete, a .csv file is generated locally. Exporting Information About Selected DB Instances @@ -25,7 +25,7 @@ Exporting Information About Selected DB Instances #. Log in to the management console. #. Click |image3| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, select the DB instances to be exported and click |image4| in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click **Export**. +#. On the **Instances** page, select the DB instances to be exported and click |image4| in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click **Export**. #. After the export task is complete, a .csv file is generated locally. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/rebooting_a_db_instance.rst b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/rebooting_a_db_instance.rst index 342de2b..046edd3 100644 --- a/umn/source/working_with_gaussdbfor_mysql/instance_modifications/rebooting_a_db_instance.rst +++ b/umn/source/working_with_gaussdbfor_mysql/instance_modifications/rebooting_a_db_instance.rst @@ -27,7 +27,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, locate the target DB instance and choose **More** > **Reboot** in the **Operation** column. +#. On the **Instances** page, locate the target DB instance and choose **More** > **Reboot** in the **Operation** column. Alternatively, click the target DB instance. On the displayed page, click **Reboot** in the upper right corner of the page. diff --git a/umn/source/working_with_gaussdbfor_mysql/interconnection_with_cts/key_operations_supported_by_cts.rst b/umn/source/working_with_gaussdbfor_mysql/interconnection_with_cts/key_operations_supported_by_cts.rst index 60dd061..0eb326e 100644 --- a/umn/source/working_with_gaussdbfor_mysql/interconnection_with_cts/key_operations_supported_by_cts.rst +++ b/umn/source/working_with_gaussdbfor_mysql/interconnection_with_cts/key_operations_supported_by_cts.rst @@ -60,3 +60,5 @@ Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for f +----------------------------------------------+----------------+-----------------------+ | Applying a parameter template | parameterGroup | applyParameterGroup | +----------------------------------------------+----------------+-----------------------+ + | Deleting a task from the task center | job | deleteTaskCenterJob | + +----------------------------------------------+----------------+-----------------------+ diff --git a/umn/source/working_with_gaussdbfor_mysql/logs/viewing_error_logs.rst b/umn/source/working_with_gaussdbfor_mysql/logs/viewing_error_logs.rst index 44ceccd..9f94de8 100644 --- a/umn/source/working_with_gaussdbfor_mysql/logs/viewing_error_logs.rst +++ b/umn/source/working_with_gaussdbfor_mysql/logs/viewing_error_logs.rst @@ -13,7 +13,7 @@ Viewing Log Details #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the navigation pane on the left, choose **Logs**. #. On the **Error Logs** page, select a node and view the error log details of the node, including: diff --git a/umn/source/working_with_gaussdbfor_mysql/logs/viewing_slow_query_logs.rst b/umn/source/working_with_gaussdbfor_mysql/logs/viewing_slow_query_logs.rst index 8664334..566b258 100644 --- a/umn/source/working_with_gaussdbfor_mysql/logs/viewing_slow_query_logs.rst +++ b/umn/source/working_with_gaussdbfor_mysql/logs/viewing_slow_query_logs.rst @@ -29,7 +29,7 @@ Viewing Log Details #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the navigation pane on the left, choose **Logs**. diff --git a/umn/source/working_with_gaussdbfor_mysql/monitoring/viewing_monitoring_metrics.rst b/umn/source/working_with_gaussdbfor_mysql/monitoring/viewing_monitoring_metrics.rst index a4a5c88..b93ed37 100644 --- a/umn/source/working_with_gaussdbfor_mysql/monitoring/viewing_monitoring_metrics.rst +++ b/umn/source/working_with_gaussdbfor_mysql/monitoring/viewing_monitoring_metrics.rst @@ -38,7 +38,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, locate the target DB instance and click **View Metric** in the **Operation** column to go to the Cloud Eye console. +#. 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: diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/applying_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/applying_a_parameter_template.rst index dd4c2bf..6d5af33 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/applying_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/applying_a_parameter_template.rst @@ -22,7 +22,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, you can apply a default template or a custom template to a target DB instance: +#. On the **Parameter Templates** page, you can apply a default template or a custom template to a target DB instance: - To apply a default template, click **Default Templates**, locate the target parameter template, and in the **Operation** column, click **Apply**. - To apply a custom template, click **Custom Templates**, locate the target parameter template, and in the **Operation** column, choose **More** > **Apply**. diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/comparing_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/comparing_a_parameter_template.rst index 126e104..da073d8 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/comparing_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/comparing_a_parameter_template.rst @@ -18,7 +18,7 @@ Comparing Instance Parameters with a Parameter Template #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. In the navigation pane on the left, choose **Parameters**. On the displayed page, click **Compare** above the parameter list. #. In the displayed dialog box, select a parameter template to be compared and click **OK**. @@ -31,7 +31,7 @@ Comparing Parameter Templates #. Log in to the management console. #. Click |image2| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, click **Custom Templates**. Locate the target parameter template and click **Compare** in the **Operation** column. +#. On the **Parameter Templates** page, click **Custom Templates**. Locate the target parameter template and click **Compare** in the **Operation** column. #. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click **OK**. - If their settings are different, the parameter names and values of both parameter templates are displayed. diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/creating_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/creating_a_parameter_template.rst index 88e4d7b..2f385e8 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/creating_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/creating_a_parameter_template.rst @@ -26,7 +26,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, click **Create Parameter Template**. +#. On the **Parameter Templates** page, click **Create Parameter Template**. #. In the displayed dialog box, configure required information and click **OK**. - Select a DB engine for the parameter template. diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/deleting_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/deleting_a_parameter_template.rst index f9073e4..a43b201 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/deleting_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/deleting_a_parameter_template.rst @@ -21,7 +21,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, click **Custom Templates**. Locate the parameter template to be deleted and choose **More** > **Delete** in the **Operation** column. +#. On the **Parameter Templates** page, click **Custom Templates**. Locate the parameter template to be deleted and choose **More** > **Delete** in the **Operation** column. #. In the displayed dialog box, click **Yes**. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/exporting_parameters.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/exporting_parameters.rst index d117bb7..99da6f0 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/exporting_parameters.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/exporting_parameters.rst @@ -20,7 +20,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. In the navigation pane on the left, choose **Parameters**. On the displayed page, click **Export** above the parameter list. diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template.rst index 33c3dd7..24df409 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template.rst @@ -22,7 +22,7 @@ Modifying Parameter Template Parameters #. Click **Service List**. Under **Database**, click **GaussDB**. -#. In the navigation pane on the left, choose **Parameter Template Management**. On the **Custom Templates** page, click the parameter template you want to view. +#. In the navigation pane on the left, choose **Parameter Templates**. On the **Custom Templates** page, click the parameter template you want to view. #. Modify parameters as required. @@ -54,7 +54,7 @@ Modifying Instance Parameters #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. The **Basic Information** page is displayed. +#. On the **Instances** page, click the target DB instance. The **Basic Information** page is displayed. #. In the navigation pane on the left, choose **Parameters**. On the displayed page, modify parameters as required. @@ -64,7 +64,7 @@ Modifying Instance Parameters Check the value in the **Effective upon Reboot** column. - - If the value is **Yes** and the DB instance status on the **Instance Management** page is **Pending reboot**, you must reboot the DB instance for the modifications of this parameter to take effect. + - If the value is **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**. diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template_description.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template_description.rst index eb8e84a..b8266aa 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template_description.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/modifying_a_parameter_template_description.rst @@ -20,7 +20,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, click **Custom Templates**. Locate the parameter template you want to modify and click |image2| in the **Description** column. +#. On the **Parameter Templates** page, click **Custom Templates**. Locate the parameter template you want to modify and click |image2| in the **Description** column. #. Enter a new description. You can click |image3| to submit or |image4| to cancel the modification. - After you submit the modification, you can view the new description in the **Description** column. diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/replicating_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/replicating_a_parameter_template.rst index a2f1beb..42ca0c2 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/replicating_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/replicating_a_parameter_template.rst @@ -23,15 +23,15 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, click **Custom Templates**. Locate the target parameter template and click **Replicate** in the **Operation** column. +#. On the **Parameter Templates** page, click **Custom Templates**. Locate the target parameter template and click **Replicate** in the **Operation** column. - Alternatively, click the target DB instance on the **Instance Management** page. On the **Parameters** page, click **Export** to generate a new parameter template for future use. + Alternatively, click the target DB instance on the **Instances** page. On the **Parameters** page, click **Export** to generate a new parameter template for future use. #. In the displayed dialog box, configure required details and click **OK**. - The template name consists of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.). - The template description consists of a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'= - After the parameter template is replicated, a new template is generated in the list in the **Customer Templates** tab of the **Parameter Template Management** page. + After the parameter template is replicated, a new template is generated in the list in the **Customer Templates** tab of the **Parameter Templates** page. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/resetting_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/resetting_a_parameter_template.rst index e5d04c8..6ee443f 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/resetting_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/resetting_a_parameter_template.rst @@ -16,7 +16,7 @@ Procedure #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Parameter Template Management** page, click **Custom Templates**. Locate the target parameter template and choose **More** > **Reset** in the **Operation** column. +#. On the **Parameter Templates** page, click **Custom Templates**. Locate the target parameter template and choose **More** > **Reset** in the **Operation** column. #. Click **Yes**. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_application_records_of_a_parameter_template.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_application_records_of_a_parameter_template.rst index f2082d3..b1529a2 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_application_records_of_a_parameter_template.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_application_records_of_a_parameter_template.rst @@ -19,7 +19,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. Choose **Parameter Template Management** in the navigation pane on the left, locate the target parameter template, and click **View Application Record** in the **Operation** column on the **Default Templates** page or choose **More** > **View Application Record** on the **Custom Templates** page. +#. 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/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_parameter_change_history.rst b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_parameter_change_history.rst index ddbf6af..d7c6cf8 100644 --- a/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_parameter_change_history.rst +++ b/umn/source/working_with_gaussdbfor_mysql/parameter_template_management/viewing_parameter_change_history.rst @@ -23,7 +23,7 @@ Viewing Change History of DB Instance Parameters #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. In the navigation pane on the left, choose **Parameters**. On the displayed page, click **Change History**. @@ -40,7 +40,7 @@ Viewing Change History of a Parameter Template #. Click **Service List**. Under **Database**, click **GaussDB**. -#. Choose **Parameter Template Management** in the navigation pane on the left. On the **Custom Templates** page, click the target parameter template. +#. Choose **Parameter Templates** in the navigation pane on the left. On the **Custom Templates** page, click the target parameter template. #. On the displayed page, choose **Change History** in the navigation pane on the left. diff --git a/umn/source/working_with_gaussdbfor_mysql/read_replicas/creating_a_read_replica.rst b/umn/source/working_with_gaussdbfor_mysql/read_replicas/creating_a_read_replica.rst index aaeb7af..cf2c03b 100644 --- a/umn/source/working_with_gaussdbfor_mysql/read_replicas/creating_a_read_replica.rst +++ b/umn/source/working_with_gaussdbfor_mysql/read_replicas/creating_a_read_replica.rst @@ -24,7 +24,7 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, locate the target DB instance and choose **More** > **Create Read Replica** in the **Operation** column. +#. 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 |image2| to create read replicas. diff --git a/umn/source/working_with_gaussdbfor_mysql/read_replicas/deleting_a_read_replica.rst b/umn/source/working_with_gaussdbfor_mysql/read_replicas/deleting_a_read_replica.rst index d9ac289..afc83a8 100644 --- a/umn/source/working_with_gaussdbfor_mysql/read_replicas/deleting_a_read_replica.rst +++ b/umn/source/working_with_gaussdbfor_mysql/read_replicas/deleting_a_read_replica.rst @@ -8,7 +8,7 @@ Deleting a Read Replica Scenarios --------- -You can manually delete read replicas on the **Instance Management** page. +You can manually delete read replicas on the **Instances** page. .. important:: @@ -29,12 +29,12 @@ Procedure #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. At the bottom of the **Basic Information** page, locate the read replicas to be deleted and choose **More** > **Delete** in the **Operation** column. For high availability reasons, the system reserves an available read replica. The read replica cannot be deleted until the associated DB instance is deleted. -#. In the displayed dialog box, click **Yes**. Refresh the **Instance Management** page later to check that the deletion is successful. +#. In the displayed dialog box, click **Yes**. Refresh the **Instances** page later to check that the deletion is successful. .. |image1| image:: /_static/images/en-us_image_0000001352219100.png diff --git a/umn/source/working_with_gaussdbfor_mysql/read_replicas/promoting_a_read_replica_to_the_primary_node.rst b/umn/source/working_with_gaussdbfor_mysql/read_replicas/promoting_a_read_replica_to_the_primary_node.rst index 77cd45b..3354870 100644 --- a/umn/source/working_with_gaussdbfor_mysql/read_replicas/promoting_a_read_replica_to_the_primary_node.rst +++ b/umn/source/working_with_gaussdbfor_mysql/read_replicas/promoting_a_read_replica_to_the_primary_node.rst @@ -15,7 +15,7 @@ Manual Switchover #. Log in to the management console. #. Click |image1| in the upper left corner and select a region and a project. #. Click **Service List**. Under **Database**, click **GaussDB**. -#. On the **Instance Management** page, click the target DB instance. +#. On the **Instances** page, click the target DB instance. #. At the bottom of the **Basic Information** page, locate the read replica to be promoted and click **Promote to Primary** in the **Operation** column. #. In the displayed dialog box, click **Yes**.