From 502af82209c7614b1436d1e834e3695586ff227a Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Wed, 13 Dec 2023 11:08:30 +0000 Subject: [PATCH] Update content --- .../splitting_read_and_write_requests.rst | 9 +++++---- ...eate_a_ddm_instance_and_an_rds_for_mysql_instance.rst | 6 +++++- .../instance_management/creating_a_ddm_instance.rst | 6 +++++- .../editing_a_parameter_template.rst | 2 +- .../schema_management/configuring_the_sql_blacklist.rst | 2 +- umn/source/tags.rst | 6 +++++- umn/source/task_center.rst | 7 ++++++- 7 files changed, 28 insertions(+), 10 deletions(-) diff --git a/umn/source/data_node_management/splitting_read_and_write_requests.rst b/umn/source/data_node_management/splitting_read_and_write_requests.rst index ae0450c..3377003 100644 --- a/umn/source/data_node_management/splitting_read_and_write_requests.rst +++ b/umn/source/data_node_management/splitting_read_and_write_requests.rst @@ -26,13 +26,14 @@ Procedure #. On the **Instances** page, locate the required DDM instance and click its name. #. In the navigation pane, choose **Data Nodes**. -#. On the displayed page, locate the target instance and click **Configure Read Weight** in the **Operation** column. - - - The read weight ranges from 0 to 100. +#. On the displayed page, locate the target instance and click **Configure Read Weight** in the **Operation** column. The read weight ranges from 0 to 100. - If you create a read replica for the associated instance, the read replica will handle all separated read requests by default. To re-assign read/write requests, you can configure read weights of the associated instance and its read replica. - - After the read weights are configured, the primary instance and its read replica will handle read requests according to the ratio: Read weight of primary instance/Total read weights of primary instance and read replica: Read weight of read replica/Total read weights of primary instance and read replica. + - After a read weight is set for an instance, the primary instance and its read replica process read requests based on the following formula: + + - Read requests processed by the primary instance: Read weight of the primary instance/Total read weights of the primary instance and its read replica + - Read requests processed by the read replica: Read weights of the read replica/Total read weights of the primary instance and its read replica For example: If an RDS for MySQL instance contains one primary instance and one read replica and read weights of the primary instance and its read replica are 20 and 80 respectively, they will process read requests in the ratio of 1:4. In other words, the primary instance processes 1/4 of read requests and read replica processes 3/4. Write requests are automatically routed to the primary instance. diff --git a/umn/source/getting_started/step_1_create_a_ddm_instance_and_an_rds_for_mysql_instance.rst b/umn/source/getting_started/step_1_create_a_ddm_instance_and_an_rds_for_mysql_instance.rst index 837762f..95cde68 100644 --- a/umn/source/getting_started/step_1_create_a_ddm_instance_and_an_rds_for_mysql_instance.rst +++ b/umn/source/getting_started/step_1_create_a_ddm_instance_and_an_rds_for_mysql_instance.rst @@ -76,12 +76,14 @@ Procedure +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Tags | (Optional) Adding tags helps you better identify and manage your DDM resources. | | | | - | | You can add tags to your DDM instance. Each instance can have a maximum of 10 tags. | + | | You can add tags to your instance. Each instance can have a maximum of 20 tags. | | | | | | **Tag key: This parameter is mandatory and cannot be null.** | | | | | | - Must be unique for each instance. | | | | + | | - Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@). | + | | | | | - Can include 1 to 36 characters. | | | | | | - Cannot be an empty string or start with **\_sys\_**, and cannot start or end with a space. | @@ -94,6 +96,8 @@ Procedure | | | | | - Is an empty string by default. | | | | + | | - Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@). | + | | | | | - Can contain 0 to 43 characters. | | | | | | - Cannot contain the following characters: | diff --git a/umn/source/instance_management/creating_a_ddm_instance.rst b/umn/source/instance_management/creating_a_ddm_instance.rst index 37cbb4d..5a11eb1 100644 --- a/umn/source/instance_management/creating_a_ddm_instance.rst +++ b/umn/source/instance_management/creating_a_ddm_instance.rst @@ -74,12 +74,14 @@ Procedure +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Tags | (Optional) Adding tags helps you better identify and manage your DDM resources. | | | | - | | You can add tags to your DDM instance. Each instance can have a maximum of 10 tags. | + | | You can add tags to your instance. Each instance can have a maximum of 20 tags. | | | | | | **Tag key: This parameter is mandatory and cannot be null.** | | | | | | - Must be unique for each instance. | | | | + | | - Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@). | + | | | | | - Can include 1 to 36 characters. | | | | | | - Cannot be an empty string or start with **\_sys\_**, and cannot start or end with a space. | @@ -92,6 +94,8 @@ Procedure | | | | | - Is an empty string by default. | | | | + | | - Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@). | + | | | | | - Can contain 0 to 43 characters. | | | | | | - Cannot contain the following characters: | diff --git a/umn/source/parameter_template_management/editing_a_parameter_template.rst b/umn/source/parameter_template_management/editing_a_parameter_template.rst index ff0da8c..2e58c7f 100644 --- a/umn/source/parameter_template_management/editing_a_parameter_template.rst +++ b/umn/source/parameter_template_management/editing_a_parameter_template.rst @@ -7,7 +7,7 @@ Editing a Parameter Template To improve performance of a DDM instance, you can modify parameters in custom parameter templates based on service requirements. -You cannot change parameter values in default parameter templates. When you change parameter values in a custom parameter template, the changes take effect for all instances to which the parameter template applies. +You cannot change parameter values in default parameter templates. The following are the key points you should know when using parameters from a parameter template: diff --git a/umn/source/schema_management/configuring_the_sql_blacklist.rst b/umn/source/schema_management/configuring_the_sql_blacklist.rst index d214806..86c7011 100644 --- a/umn/source/schema_management/configuring_the_sql_blacklist.rst +++ b/umn/source/schema_management/configuring_the_sql_blacklist.rst @@ -27,7 +27,7 @@ Procedure .. note:: - **Prefix Match**: Enter SQL statements that contain keywords such as DROP or DELETE and are not allowed by the current schema. - - **Full-text Match**: Enter full-text SQL statements that are not allowed by the current schema. + - **Full-text Match**: Enter full-text SQL statements that are not allowed by the current schema. Multiple spaces and line breaks will not be treated as if they were replaced or truncated as a single space. - **Regular Expression Match**: Enter specific regular expressions that are not allowed by the current schema. - Separate SQL statements in the blacklist with semicolons (;). The size of SQL statements for prefix match, full-text match, and regular expression match cannot exceed 1 KB, respectively. - If you want to clear all the SQL statements in prefix match and full-text match areas, clear them separately and click **OK**. diff --git a/umn/source/tags.rst b/umn/source/tags.rst index f836a16..a309fdb 100644 --- a/umn/source/tags.rst +++ b/umn/source/tags.rst @@ -11,7 +11,7 @@ Precautions ----------- - A tag consists of a key and value. You can add only one value for each key. -- Each instance can have up to 10 tags. +- Each instance can have up to 20 tags. Adding a tag ------------ @@ -37,6 +37,8 @@ Adding a tag | | | | | - Must be unique for each instance. | | | | + | | - Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@). | + | | | | | - Can include 1 to 36 characters. | | | | | | - Cannot be an empty string or start with **\_sys\_**, and cannot start or end with a space. | @@ -49,6 +51,8 @@ Adding a tag | | | | | - Is an empty string by default. | | | | + | | - Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@). | + | | | | | - Can contain 0 to 43 characters. | | | | | | - Cannot contain the following characters: | diff --git a/umn/source/task_center.rst b/umn/source/task_center.rst index 1ee2ba0..f80a4dd 100644 --- a/umn/source/task_center.rst +++ b/umn/source/task_center.rst @@ -21,7 +21,12 @@ You can view the progress and results of asynchronous tasks on the **Task Center - Unbinding an EIP from a DDM instance - Restoring data from current DDM instance - Importing schema information - - Flexible shard configuration + - Configuring shards + - Retrying shard configuration + - Deleting a backup + - Creating a group + - Deleting a group + - Restarting the node Procedure ---------