Skip to content

Propagate changes to distributed-database-middleware-api-ref from PreProd environment #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
otcbot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Propagate changes to distributed-database-middleware-api-ref from PreProd environment #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion umn/source/backups_and_restorations/restoring_metadata.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ Restoring Metadata Using Backups

#. In the DDM instance list, locate the source instance and click its name.

#. In the navigation pane on the left, choose **Backups**.
#. In the navigation pane on the left, choose **Backups**. Alternatively, go to the instance details page and choose **Backups** in the navigation pane on the left.

#. Locate the required backup based on the instance name and backup time and click **Restore** in the **Operation** column.

Expand Down
2 changes: 1 addition & 1 deletion .../getting_started/step_1_create_a_ddm_instance_and_an_rds_for_mysql_instance.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ Procedure
| | - Must be 4 to 64 characters long. |
| | - Can contain only letters, digits, and hyphens (-). |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Node Class | Class of the DDM instance node. You can select **General-enhanced** or **Kunpeng general computing-plus** and then specify a node class. |
| Node Class | Class of the DDM instance node. You can select **General-enhanced** and then specify a node class. |
| | |
| | .. note:: |
| | |
Expand Down
2 changes: 1 addition & 1 deletion umn/source/instance_management/creating_a_ddm_instance.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Procedure
| | - Must be 4 to 64 characters long. |
| | - Can contain only letters, digits, and hyphens (-). |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Node Class | Class of the DDM instance node. You can select **General-enhanced** or **Kunpeng general computing-plus** and then specify a node class. |
| Node Class | Class of the DDM instance node. You can select **General-enhanced** and then specify a node class. |
| | |
| | .. note:: |
| | |
Expand Down
42 changes: 19 additions & 23 deletions umn/source/monitoring_management/supported_metrics/network_metrics.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,26 +9,22 @@ If load balancing is enabled for your DDM instance, you can view network metrics

.. table:: **Table 1** Load balancing metrics

+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| Metric ID | Metric Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) |
+=====================+==================================+==================================================================================+=============+=========================+================================+
| m7_in_Bps | Inbound Rate | Traffic used for accessing the monitored object from the Internet per second | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: byte/s | | | |
+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| m8_out_Bps | Outbound Rate | Traffic used by the monitored object to access the Internet per second | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: byte/s | | | |
+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| m9_abnormal_servers | Unhealthy Servers | Number of unhealthy backend servers associated with the monitored object | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: count | | | |
+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| ma_normal_servers | Healthy Servers | Number of healthy backend servers associated with the monitored object | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: count | | | |
+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| l4_in_bps_usage | Layer-4 Inbound Bandwidth Usage | Percentage of inbound TCP/UDP bandwidth from the monitored object to the client | 0-100 | Dedicated load balancer | 1 minute |
+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| l4_out_bps_usage | Layer-4 Outbound Bandwidth Usage | Percentage of outbound TCP/UDP bandwidth from the monitored object to the client | 0-100 | Dedicated load balancer | 1 minute |
+---------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
+-------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| Metric ID | Metric Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) |
+===================+==================================+==================================================================================+=============+=========================+================================+
| m7_in_Bps | Inbound Rate | Traffic used for accessing the monitored object from the Internet per second | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: byte/s | | | |
+-------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| m8_out_Bps | Outbound Rate | Traffic used by the monitored object to access the Internet per second | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: byte/s | | | |
+-------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| ma_normal_servers | Healthy Servers | Number of healthy backend servers associated with the monitored object | >= 0 | Dedicated load balancer | 1 minute |
| | | | | | |
| | | Unit: count | | | |
+-------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| l4_in_bps_usage | Layer-4 Inbound Bandwidth Usage | Percentage of inbound TCP/UDP bandwidth from the monitored object to the client | 0-100 | Dedicated load balancer | 1 minute |
+-------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
| l4_out_bps_usage | Layer-4 Outbound Bandwidth Usage | Percentage of outbound TCP/UDP bandwidth from the monitored object to the client | 0-100 | Dedicated load balancer | 1 minute |
+-------------------+----------------------------------+----------------------------------------------------------------------------------+-------------+-------------------------+--------------------------------+
4 changes: 2 additions & 2 deletions umn/source/schema_management/creating_a_schema.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Prerequisites
- The internal account name is in the format: Fixed prefix (such as DDMRW, DDMR, or DDMREP) + Hash value of the data node ID.
- A random password is generated, which contains 16 to 32 characters.
- All instances associated with one schema must have the same major MySQL version.
- Multiple schemas can be created in a DDM instance and associated with the same data node. One DDM instance can be associated with either RDS for MySQL or GaussDB(for MySQL) instances, but not both, and it cannot be associated with multiple RDS for MySQL instances with different versions. Otherwise, metadata restoration will fail.
- Multiple schemas can be created in a DDM instance and associated with the same data node. One DDM instance cannot be associated with multiple RDS for MySQL instances with different versions at the same time. Otherwise, metadata restoration will fail.
- One data node cannot be associated with schemas in different DDM instances.
- If you create a sharded schema, more than one shard will be generated in the schema. Shard names follow the rule: *<schemaname>*\ \_\ *<number>*. *<number>* here indicates a four-digit number starting from 0000. This number will be incremented by one. For example, if a schema name is **db_cbb5** and there are 2 shards, the shard names are **db_cbb5_0000** and **db_cbb5_0001**.
- Read-only instances cannot be associated with the schema as data nodes.
Expand All @@ -37,7 +37,7 @@ Procedure
| Parameter | Description |
+===================================+=============================================================================================================================================================================================================================+
| Sharding | - **Sharded**: indicates that one schema can be associated with multiple data nodes, and all shards will be evenly distributed across the nodes. |
| | - **Unsharded**: indicates that one schema can be associated with only one data node, and only one shard can be created on the RDS instance. |
| | - **Unsharded**: indicates that one schema can be associated with only one data node, and only one shard can be created on the data node. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Schema | The name contains 2 to 48 characters and must start with a lowercase letter. Only lowercase letters, digits, and underscores (_) are allowed. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Expand Down