Resetting the consumer offset
|
Messages may be consumed more than once after the offset is reset.
diff --git a/docs/dms_rocketmq/umn/hrm-pd-011.html b/docs/dms_rocketmq/umn/hrm-pd-011.html
deleted file mode 100644
index effc39f90..000000000
--- a/docs/dms_rocketmq/umn/hrm-pd-011.html
+++ /dev/null
@@ -1,298 +0,0 @@
-
-
-Permissions Management
-You can use Identity and Access Management (IAM) to manage DMS permissions and control access to your resources. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.
- You can create IAM users for your employees, and assign permissions to these users on a principle of least privilege (PoLP) basis to control their access to specific resource types. For example, you can create IAM users for software developers and assign specific permissions to allow them to use DMS for RocketMQ resources but prevent them from being able to delete resources or perform any high-risk operations.
- If your account does not require individual IAM users for permissions management, skip this section.
- IAM is free of charge. You pay only for the resources in your account. For more information, see IAM Service Overview.
- DMS PermissionsBy default, new IAM users do not have any permissions assigned. To assign permissions to these new users, add them to one or more groups, and attach permissions policies or roles to these groups.
- DMS is a project-level service deployed and accessed in specific physical regions. When assigning DMS for RocketMQ permissions to a user group, specify region-specific projects where the permissions will take effect. If you select All projects, the permissions will be granted for all region-specific projects. When accessing DMS, the users need to switch to a region where they have been authorized to use this service.
- You can grant users permissions by using roles and policies. - Roles: A type of coarse-grained authorization mechanism that provides only a limited number of service-level roles. When using roles to grant permissions, you also need to assign dependency roles. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization for more secure access control. For example, you can grant IAM users only the permissions for managing DMS instances. Most policies define permissions based on APIs. For the API actions supported by DMS, see Permissions and Supported Actions.
-
- Table 1 lists all the system-defined roles and policies supported by DMS.
-
- Table 1 System-defined roles and policies supported by DMSRole/Policy Name
- |
-Description
- |
-Type
- |
-Dependencies
- |
-
|---|
-
-DMS FullAccess
- |
-Administrator permissions for DMS. Users granted these permissions can perform all operations on DMS.
- |
-System-defined policy
- |
-None
- |
-
-DMS UserAccess
- |
-Common user permissions for DMS, excluding permissions for creating, modifying, deleting, and scaling up instances.
- |
-System-defined policy
- |
-None
- |
-
-DMS ReadOnlyAccess
- |
-Read-only permissions for DMS. Users granted these permissions can only view DMS data.
- |
-System-defined policy
- |
-None
- |
-
-DMS VPCAccess
- |
-VPC operation permissions to assign to DMS agencies.
- |
-System-defined policy
- |
-None
- |
-
-DMS KMSAccess
- |
-KMS operation permissions to assign to DMS agencies.
- |
-System-defined policy
- |
-None
- |
-
-DMS Administrator
- |
-Administrator permissions for DMS.
- |
-System-defined role
- |
-This role depends on the Tenant Guest and VPC Administrator roles.
- |
-
-DMS ELBAccess
- |
-ELB operation permissions to assign to DMS agencies.
- |
-System-defined policy
- |
-None
- |
-
-DMS VPCEndpointAccess
- |
-VPC endpoint operation permissions to assign to DMS agencies.
- |
-System-defined policy
- |
-None
- |
-
-DMSAgencyCheckAccessPolicy
- |
-IAM operation permissions to assign to DMS agencies.
- |
-System-defined policy
- |
-None
- |
-
-
-
-
- lists the common operations supported by each DMS for RocketMQ system policy or role. Select the policies or roles as required.
-
- Table 2 Common operations supported by each system-defined policy or role of DMS for RocketMQOperation
- |
-DMS FullAccess
- |
-DMS UserAccess
- |
-DMS ReadOnlyAccess
- |
-DMS VPCAccess
- |
-DMS KMSAccess
- |
-DMS ELBAccess
- |
-DMS VPCEndpointAccess
- |
-DMSAgencyCheckAccessPolicy
- |
-
|---|
-
-Creating an instance
- |
-√
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-
-Modifying instances
- |
-√
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-
-Deleting instances
- |
-√
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-
-Modifying instance specifications
- |
-√
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-
-Querying instance information
- |
-√
- |
-√
- |
-√
- |
-×
- |
-×
- |
-×
- |
-×
- |
-×
- |
-
-
-
-
-
- Fine-grained AuthorizationTo use a custom fine-grained policy, log in to the IAM console as an administrator and select the desired fine-grained permissions for DMS. Table 3 describes fine-grained permission dependencies of DMS for RocketMQRocketMQ instances in DMS.
-
- Table 3 Fine-grained permission dependencies of DMS for RocketMQRocketMQ instances in DMSPermission
- |
-Description
- |
-Dependency
- |
-
|---|
-
-dms:instance:list
- |
-Viewing the instance list
- |
-None
- |
-
-dms:instance:get
- |
-Viewing instance details
- |
-None
- |
-
-dms:instance:create
- |
-Creating an instance
- |
-- vpc:vpcs:get
- vpc:ports:create
- vpc:securityGroups:get
- vpc:ports:get
- vpc:subnets:get
- vpc:vpcs:list
- vpc:publicIps:get
- vpc:publicIps:list
- vpc:ports:update
- vpc:publicIps:update
- vpc:ports:delete
- |
-
-dms:instance:getBackgroundTask
- |
-Viewing background task details
- |
-None
- |
-
-dms:instance:deleteBackgroundTask
- |
-Deleting a background task
- |
-None
- |
-
-dms:instance:modify
- |
-Modifying an instance
- |
-- vpc:vpcs:get
- vpc:ports:create
- vpc:securityGroups:get
- vpc:ports:get
- vpc:subnets:get
- vpc:vpcs:list
- vpc:publicIps:get
- vpc:publicIps:list
- vpc:ports:update
- vpc:publicIps:update
- vpc:ports:delete
- |
-
-dms:instance:delete
- |
-Deleting an instance
- |
-None
- |
-
-
-
-
-
- Getting Started with RocketMQ to Produce and Consume Messages
-This document takes the example of creating a RocketMQ instance with SSL enabled and accessing it on a client in the same VPC as the instance over a private network for message production and consumption to get you quickly started with Distributed Message Service (DMS).
- ProcedureFigure 1 Procedure for using DMS for RocketMQ
+ This document takes the example of creating a RocketMQ instance with SSL enabled and accessing it on a client in the same VPC as the instance over a private network for message production and consumption to get you quickly started with Distributed Message Service (DMS) for RocketMQ.
+ ProcedureFigure 1 Procedure for using DMS for RocketMQ
- Step 1: Preparations
A RocketMQ instance runs in a VPC. Before creating a RocketMQ instance, ensure that a VPC is available.
- Step 2: Create a RocketMQ Instance
Enable SSL, disable ACL, and configure the created VPC and subnet, and security group.
- Step 3: Create a Topic
After an instance is created, create a topic for sending and receiving messages.
@@ -63,14 +63,14 @@
 After a security group is created, its default inbound rule allows communication among ECSs within the security group and its default outbound rule allows all outbound traffic. In this case, you can access a RocketMQ instance within a VPC, and do not need to add rules according to Table 1.
- Create an elastic cloud server (ECS) and configure environment variables.
The following takes a Linux ECS as an example. For more information about how to install JDK and configure the environment variables for a Windows ECS, please search the Internet.
-- Log in to the console, click
 in the upper left corner, click Elastic Cloud Server under Computing, and then create an ECS.For details, see Creating an ECS. If you already have an available ECS, skip this step.
- - Log in to an ECS as user root.
- Install the JDK and configure the environment variables JAVA_HOME and PATH.
- Download the JDK.
Use Oracle JDK instead of ECS's default JDK (for example, OpenJDK), because ECS's default JDK may not be suitable for the sample project. Obtain Oracle JDK 1.8.111 or later from Oracle's official website.
+ - Log in to the console, click in the upper left corner, click Elastic Cloud Server under Computing, and then create an ECS.
For details, see Creating an ECS. If you already have an available ECS, skip this step.
+ - Log in to an ECS as user root.
- Install the JDK and configure the environment variables JAVA_HOME and PATH.
- Download the JDK.
Use Oracle JDK instead of default ECS JDK (for example, OpenJDK), because it may not be suitable for the sample project. Obtain Oracle JDK 1.8.111 or later from Oracle's official website.
- Run the following command to decompress the JDK package.
tar -zxvf jdk-8u321-linux-x64.tar.gz
Change jdk-8u321-linux-x64.tar.gz to your JDK version.
- Run the following command to edit the environment variable file .bash_profile:
vim ~/.bash_profile
- Press i and add the following content.
export JAVA_HOME=/opt/java/jdk1.8.0_321
-export PATH=$JAVA_HOME/bin:$PATH
+export PATH=$JAVA_HOME/bin:$PATH
Change /opt/java/jdk1.8.0_321 to the path where you install JDK.
- Press Esc to exit the editing mode. Enter the following command and press Enter to save and exit the environment variable file:
:wq
- Run the following command to make the environment variables take effect:
source .bash_profile
@@ -79,108 +79,108 @@ export PATH=$JAVA_HOME/bin:$PATH
If the following information is displayed, the JDK is installed successfully: java version "1.8.0_321"
- Run the following command to download the rocketmq-tutorial sample software package.
Before downloading the sample software package, ensure that the client server can access the Internet.
-wget https://dms-demos.obs.eu-de.otc.t-systems.com/rocketmq-tutorial.zip
+wget https://dms-demo.obs.eu-de.otc.t-systems.com/rocketmq-tutorial.zip
- Run the following command to decompress rocketmq-tutorial.
unzip rocketmq-tutorial.zip
Step 2: Create a RocketMQ InstanceBefore using RocketMQ for message production and consumption, create a RocketMQ instance. The VM resource in the instance store topics.
- Log in to the DMS for RocketMQ console and click Create RocketMQ Instance in the upper right.
- Set the instance information. For details, see Table 2.
- Table 2 Setting instance informationParameter
+Table 2 Setting instance informationParameter
|
-Description
+ | Description
|
|---|
-Region
+ | Region
|
-For lower network latency and faster access to your resources, select the nearest region.
+ | For lower network latency and faster access to your resources, select the nearest region.
Select eu-de.
|
-Project
+ | Project
|
-Projects isolate compute, storage, and network resources across geographical regions. For each region, a preset project is available.
+ | Projects isolate compute, storage, and network resources across geographical regions. For each region, a preset project is available.
Select eu-de (default).
|
-AZ
+ | AZ
|
-Select one as required. You are advised to specify multiple AZs for disaster recovery.
+ | Select one as required. You are advised to specify multiple AZs for disaster recovery.
|
-Instance Name
+ | Instance Name
|
-Enter the instance name, for example, rocketmq-test.
+ | Enter the instance name, for example, rocketmq-test.
|
-Enterprise Project
+ | Enterprise Project
|
-An enterprise project manages project resources in groups. Enterprise projects are logically isolated. Select "default". This parameter is for enterprise users.
+ | An enterprise project manages project resources in groups. Enterprise projects are logically isolated. Select "default". This parameter is for enterprise users.
|
-Version
+ | Version
|
-Select an instance version. Select 5.x.
-Fixed once the instance is created. Use the same version as your client.
+ | Select an instance version. Select 5.x.
+Fixed once the RocketMQ instance is created. Use the same version as your client.
|
-Instance Type
+ | Instance Type
|
-Select an instance type. Select Basic here.
+ | Select an instance type. Select Basic here.
|
-Architecture
+ | Architecture
|
-Select an instance architecture. Select Cluster here.
+ | Select an instance architecture. Select Cluster here.
|
-Flavor
+ | Flavor
|
-Select an instance flavor. Select rocketmq.b2.large.4 here.
+ | Select an instance flavor. Select rocketmq.b2.large.4 here.
|
-Storage Space
+ | Storage Space
|
-Specify the disk type and storage space for storing RocketMQ data. Select Ultra-high I/O and enter 300.
+ | Specify the disk type and storage space for storing RocketMQ data. Select Ultra-high I/O and enter 300.
|
-VPC
+ | VPC
|
-Select a VPC and a subnet. Here, select the ones created in Step 1: Preparations.
+ | Select a VPC and a subnet. Here, select the ones created in Step 1: Preparations.
|
-Security Group
+ | Security Group
|
-Select the security group. Here, select the one created in Step 1: Preparations.
+ | Select the security group. Here, select the one created in Step 1: Preparations.
|
-SSL
+ | SSL
|
-Ciphertext access with high security, but lower performance. Select SSL.
+ | Ciphertext access with high security, but lower performance. Select SSL.
|
-ACL
+ | ACL
|
-Enabling ACL can manage permissions for message production and consumption. Do not enable it here.
+ | Enabling ACL can manage permissions for message production and consumption. Do not enable it here.
|
Advanced settings
|
-Public Access
+ | Public Access
|
-EIPs are required to enable public access. Do not enable it here.
+ | EIPs are required to enable public access. Do not enable it here.
|
-Tags
+ | Tags
|
-Identifiers of the RocketMQ instance. Skip it here.
+ | Identifiers of the RocketMQ instance. Skip it here.
|
-Description
+ | Description
|
-Additional information about the instance. Skip it.
+ | Additional information about the instance. Skip it.
|
@@ -188,13 +188,11 @@ export PATH=$JAVA_HOME/bin:$PATH
- Click Create Now.
- Confirm the instance information and submit the request.
- Return to the instance list and check whether the RocketMQ instance has been created.
It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.
- If the instance is created successfully, its status changes to Running.
- delete it. Then create a new one. If the instance creation fails again, contact .
- - After the instance is created, click its name to go to the instance overview page.
- Record the instance connection addresses for later use.
-
-
Figure 2 Recording instance connection addresses
+ - After the instance is created, click its name to go to the instance overview page.
- Record the instance connection addresses from the Connection area for later use.
Figure 2 Recording instance connection addresses
Step 3: Create a TopicA topic is the basic unit for sending and receiving messages. After creating a RocketMQ instance, you must manually create topics before creating and retrieving messages.
- - Click a RocketMQ instance to go to the instance page.
- In the navigation pane, choose Instance > Topics.
- Click Create Topic.
- Configure the topic name and other parameters by referring to Table 3.
+ - Click a RocketMQ instance to go to the instance overview page.
- In the navigation pane, choose Instance > Topics.
- Click Create Topic.
- Configure the topic name and other parameters by referring to Table 3.
Table 3 Topic parametersParameter
|
Description
@@ -219,12 +217,11 @@ export PATH=$JAVA_HOME/bin:$PATH
|
|---|
- Click OK.
Step 4: Connect to a RocketMQ Instance to Produce and Consume Messages- Go to the rocketmq-tutorial/bin directory on the ECS.
cd rocketmq-tutorial/bin
- Produce normal messages by the following commands.
The following is a command example: JAVA_OPT=-Dtls.enable=true sh mqadmin sendMessage -n "10.xxx.xxx.89:8100;10.xxx.xxx.144:8100" -t Topic01 -p "hello rocketmq"
- - 10.xxx.xxx.89:8100;10.xxx.xxx.144:8100: the connection address of the RocketMQ instance, that is, the connection address in 7.
- Topic01: name of the topic created in 4 for the RocketMQ instance.
- hello rocketmq: the produced message content, can be customized.
+ - 10.xxx.xxx.89:8100;10.xxx.xxx.144:8100: the connection address of the RocketMQ instance, that is, the connection address in 7.
- Topic01: name of the topic created in 4 for the RocketMQ instance.
- hello rocketmq: the produced message content, can be customized.
- Consume normal messages by the following commands.
The following is a command example: JAVA_OPT=-Dtls.enable=true sh mqadmin consumeMessage -n "10.xxx.xxx.89:8100;10.xxx.xxx.144:8100" -t Topic01
diff --git a/docs/dms_rocketmq/umn/hrm-ug-002.html b/docs/dms_rocketmq/umn/hrm-ug-002.html
index c059478e0..a0b823e1f 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-002.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-002.html
@@ -116,31 +116,31 @@
Creating a RocketMQ Instance- Log in to the console.
- Click
 in the upper left corner to select a region.DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click
 and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ. - Click Create RocketMQ Instance in the upper right corner of the page.
- Select a Region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+Creating a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest region for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click Create RocketMQ Instance in the upper right corner of the page.
- Select a Region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- Select a Project.
Projects isolate compute, storage, and network resources across geographical regions. For each region, a preset project is available.
- Select an AZ.
An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.
Select AZs as prompted based on the instance version.
- Enter an Instance Name.
You can customize a name that complies with the rules: 4–64 characters; starts with a letter; can contain only letters, digits, hyphens (-), and underscores (_).
- Select an Enterprise Project.
This parameter is for enterprise users. An enterprise project manages cloud resources. The enterprise project management service unifies cloud resources in projects, and resources and members in a project. The default project is default.
- - Configure the following instance parameters:
- Version: Only 5.x is available.
- Architecture: Retain the default value.
- Single-node: There is only one RocketMQ broker. The single-node architecture can only be used for testing.
- Cluster: There are multiple RocketMQ brokers.
+ - Configure the following instance parameters:
- Version: Only 5.x is available.
- Architecture: Retain the default value. Single-node and Cluster are available.
- Single-node: There is only one RocketMQ broker. The single-node architecture can only be used for testing.
- Cluster: There are multiple RocketMQ brokers.
- Flavor: Select the required flavor.
- Storage Space: Disk type and total storage space of each broker.
The disk type is fixed once the instance is created.
-The disk type can be high I/O, ultra-high I/O, General Purpose SSD, or Extreme SSD. For details about how to select a disk type, see Disk Types and Performance.
+The disk type can be high I/O, ultra-high I/O, general-purpose SSD, and extreme SSD. For details about how to select a disk type, see Disk Types and Performance.
- Configure the instance network parameters.
- Select the created VPC and subnet from the VPC drop-down list.
A VPC provides an isolated virtual network for your RocketMQ instances. You can configure and manage the network.
After the RocketMQ instance is created, its VPC and subnet cannot be changed.
- Select a security group.
A security group is a set of rules for accessing a RocketMQ instance.
- - Configure SSL.
- SSL: Ciphertext access with high security, but lower performance.
- PLAINTEXT: Plaintext access with high performance, but lower security.
- PERMISSIVE: Both ciphertext and plaintext access, depending on the client.
+ - Configure SSL.
- SSL: Ciphertext access with high security, but lower performance.
- PLAINTEXT: Plaintext access with high performance, but lower security.
- PERMISSIVE: Both ciphertext and plaintext access, depending on the client.
The SSL setting can be changed after the instance is created. Select a transmission mode as required.
- Configure ACL.
After ACL is enabled, the permissions for each user are exclusive.
- - Click Advanced Settings to configure more parameters.
- Configure Public Access.
Public access is disabled by default. You can enable or disable it as required. After public access is enabled, configure an IPv4 EIP for the RocketMQ instance.
+ - Click More Settings to configure more parameters.
- Configure Public Access.
Public access is disabled by default. You can enable or disable it as required. After public access is enabled, configure an IPv4 EIP for the RocketMQ instance.
- Specify tags.
Tags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify cloud resources by dimension (for example, usage, owner, or environment).
- If you have created predefined tags, select a predefined pair of tag key and value. To view or create predefined tags, click View predefined tags on the right. You will then be directed to the TMS console.
- You can also create new tags by entering Tag key and Tag value.
Up to 20 tags can be added to each RocketMQ instance. For details about the requirements on tags, see Configuring Tags for a RocketMQ Instance.
- Enter a description of the instance.
- - Click Create Now.
- Confirm the instance information, and click Submit.
- Return to the instance list and check whether the instance has been created.
It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.
-- If the instance is created successfully, its status changes to Running.
- If the instance is in the Failed state, delete it by referring to Deleting a RocketMQ Instance and try creating another one. If the instance creation fails again, contact customer service.
+ - Click Create Now.
- Confirm the instance information, and click Submit.
- Return to the instance list and check whether the instance has been created.
It takes 3 to 15 minutes to create an instance. During this period, the instance status is Creating.
+- If the instance is created successfully, its status changes to Running.
- If the instance is in the Failed state, delete it by referring to Deleting a RocketMQ Instance and try creating another one. If the instance creation fails again, contact customer service.
Viewing and Modifying Basic Information of a RocketMQ Instance
-This section describes how to view the details, and modify the basic information of a RocketMQ instance on the console.
+ This section describes how to view the details and modify the basic information of a RocketMQ instance on the console.
After creating a RocketMQ instance, you can modify some configurations of it as required, including the instance name, description, and security group.
PrerequisiteA RocketMQ instance has been created.
- Viewing Basic Information of a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Search for a RocketMQ instance by specifying the filters. Current filters include the status, name, version, instance type, specification, used/available storage space, AZ, enterprise project, and tag. For RocketMQ instance statuses, see Table 1.
+ Viewing Basic Information of a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Search for a RocketMQ instance by specifying the condition or keyword filters. Current filters include the status, name, version, instance type, specification, used/available storage space, AZ, enterprise project, and resource tag. For RocketMQ instance statuses, see Table 1.
Table 1 RocketMQ instance status descriptionStatus
|
Description
@@ -48,10 +48,10 @@
|
|---|
- Click a RocketMQ instance name to go to the instance basic information page.
+ - Click a RocketMQ instance name to go to the instance overview page.
Modifying Basic Information of a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- Modify parameters.
+ Modifying Basic Information of a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- Modify parameters.
Table 2 Connection informationParameter
|
Description
@@ -80,22 +80,22 @@
|
|---|
Public Access
|
Click  to enable or disable public access. For details, see Configuring Public Access for a RocketMQ Instance.
-Disable the public access setting of a connected RocketMQ instance interrupts the connection. As a result, messages fail to be produced and consumed.
+Disabling public access of a connected RocketMQ instance interrupts the connection. As a result, messages fail to be produced and consumed.
|
Instance Address (Public Network)
|
This parameter is displayed only when public access is enabled.
Address for connecting to the instance when public access is enabled.
-Modify the public connection address of a connected RocketMQ instance interrupts the connection. As a result, messages fail to be produced and consumed.
+Modifying the public connection address of a connected RocketMQ instance interrupts the connection. As a result, messages fail to be produced and consumed.
|
SSL
|
-Access mode of the instance, can be changed as required. For details, see Configuring SSL of a RocketMQ Instance.
+ | Access mode of the instance, which can be changed as required. For details, see Configuring SSL of a RocketMQ Instance.
Options:
-- SSL: Ciphertext access with high security, but lower performance.
- PLAINTEXT: Plaintext access with high performance, but lower security.
- PERMISSIVE: Both ciphertext and plaintext access, depending on the client.
-Modifying the access mode may have impact. For more information, see Table 1.
+- SSL: Ciphertext access with high security, but lower performance.
- PLAINTEXT: Plaintext access with high performance, but lower security.
- PERMISSIVE: Both ciphertext and plaintext access, depending on the client.
+Modifying the access mode may have an impact. For more information, see Table 1.
|
ACL
diff --git a/docs/dms_rocketmq/umn/hrm-ug-005.html b/docs/dms_rocketmq/umn/hrm-ug-005.html
index a5cd65c70..da7b65b71 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-005.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-005.html
@@ -3,11 +3,11 @@
Deleting a RocketMQ Instance
Delete one or more RocketMQ instances at a time on the DMS for RocketMQ console.
Delete one or more RocketMQ instances at a time on the DMS console.
- PrerequisitesThe RocketMQ instance is in the Running or Faulty state.
+ PrerequisiteThe RocketMQ instance is in the Running or Faulty state.
- Deleting a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Delete pay-per-use instances in either of the following ways:
- In the row containing the RocketMQ instance to be deleted, choose More > Delete.
- Click a RocketMQ instance to go to the instance details page. In the upper right corner, choose
 > Delete. - To delete multiple instances at a time, select the instances, and click Delete above the instance list.
- - In the Delete Instance dialog box, enter DELETE and click OK.
It takes 1 to 60 seconds to delete a RocketMQ instance. The instance data will be cleared.
+Deleting a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Delete pay-per-use instances in either of the following ways:
- In the row containing the RocketMQ instance to be deleted, choose More > Delete.
- Click a RocketMQ instance name to go to the instance overview page. In the upper right corner, choose > Delete.
- To delete multiple instances at a time, select the instances, and click Delete above the instance list.
+ - In the Delete Instance dialog box, enter DELETE.
- Click Yes.
It takes 1 to 60 seconds to delete a RocketMQ instance. The instance data will be cleared.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-008.html b/docs/dms_rocketmq/umn/hrm-ug-008.html
index 1c6bbdbf4..37eb4b4e2 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-008.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-008.html
@@ -1,11 +1,11 @@
Creating a RocketMQ Topic
- A topic is the basic unit for sending and receiving messages. After creating a RocketMQ instance, you must manually create a topic, and publish and subscribe messages. A message producer sends messages to this topic. A message consumer consumes messages by subscribing to this topic.
- PrerequisitesA RocketMQ instance has been created.
+ A topic is the basic unit for sending and receiving messages. After creating a RocketMQ instance, you must manually create a topic, and publish and subscribe to messages. A message producer sends messages to this topic. A message consumer consumes messages by subscribing to this topic.
+ PrerequisiteA RocketMQ instance has been created.
- Creating a Topic- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Topics.
- Click Create Topic.
- Configure the topic name and other parameters by referring toTable 1.
Figure 1 Creating a topic
+Creating a Topic- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Topics.
- Click Create Topic.
- Configure the topic name and other parameters by referring toTable 1.
Figure 1 Creating a topic
Table 1 Topic parametersParameter
|
diff --git a/docs/dms_rocketmq/umn/hrm-ug-009.html b/docs/dms_rocketmq/umn/hrm-ug-009.html
index f4e485dc4..a955a5926 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-009.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-009.html
@@ -2,11 +2,13 @@
Viewing RocketMQ Topic Details
After a topic is created, you can query its configuration and status on the console.
- Prerequisites- A RocketMQ instance has been created.
- A topic has been created.
+
- Viewing Topic Details- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Topics.
- Click the desired topic name to go to the topic details page.
The upper part of the topic details page shows the topic name, description, and message type. The lower part of the topic details page shows the total number of messages, deleted messages, topic's consumption status, and user permissions of this topic.
+Viewing Topic Details- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Topics.
- Click the desired topic name to go to the topic details page.
The upper part of the topic details page shows the topic name, description, and message type. The lower part of the topic details page shows the total number of messages, deleted messages, message consumption status, and user permissions of this topic.
Figure 1 Topic details
+ The user permission information is displayed only when you create an instance or enable ACL on the overview page of the instance.
+
diff --git a/docs/dms_rocketmq/umn/hrm-ug-010.html b/docs/dms_rocketmq/umn/hrm-ug-010.html
index 328332a7e..664571f55 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-010.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-010.html
@@ -2,10 +2,10 @@
Modifying RocketMQ Topic Configurations
The topic description can be modified as required.
- Prerequisites- A RocketMQ instance has been created.
- A topic has been created.
+
- Modifying Topic Information- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Topics.
- Modify topic parameters in either of the following ways:
- In the row containing the desired topic, click Edit.
- Click a topic to go to the topic details page and then click Edit in the upper right corner.
+Modifying Topic Information- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Topics.
- Modify topic parameters in either of the following ways:
- In the row containing the desired topic, click Edit.
- Click a topic to go to the topic details page and then click Edit in the upper right corner.
- Modify topic parameters by referring to Table 1.
Table 1 Topic parametersParameter
|
diff --git a/docs/dms_rocketmq/umn/hrm-ug-011.html b/docs/dms_rocketmq/umn/hrm-ug-011.html
index d62ee092e..7b7cc02ec 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-011.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-011.html
@@ -3,10 +3,12 @@
Deleting a RocketMQ Topic
If a topic is no longer used, you can delete it to release resources by referring to this section.
Topics can be deleted only when the instance is in the Running state.
- Prerequisites- A RocketMQ instance has been created.
- A topic has been created.
+ Notes and ConstraintsDeleting a topic clears the topic data permanently. Related services will be affected.
- Deleting a Topic- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Topics.
- Delete topics in any of the following ways:
Exercise caution when deleting topics because data will be lost.
+
+Deleting a Topic- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Topics.
- Delete topics in any of the following ways:
Exercise caution when deleting topics because data will be lost.
- In the row containing the topic to be deleted, click Delete.
- Click a topic to go to the topic details page and then click Delete in the upper right corner.
- To delete multiple topics at a time, select the topics, and click Delete Topic above the topic list.
- Click OK.
Creating a RocketMQ Consumer Group
A consumer group is a group of consumers with the same behavior and is used to manage and maintain message retrieval. A consumer can manage a type of messages using a consumer group.
- At least one RocketMQ consumer group is automatically created.
- PrerequisitesA RocketMQ instance has been created.
+ If no consumer group is created, RocketMQ automatically creates one.
+ PrerequisiteA RocketMQ instance has been created.
- Creating a RocketMQ Consumer Group- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Consumer Groups.
- Click Create Consumer Group.
- Configure the consumer group name and other parameters by referring to Table 1.
+ Creating a RocketMQ Consumer Group- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Consumer Groups.
- Click Create Consumer Group.
- Configure the consumer group name and other parameters by referring to Table 1.
Table 1 Consumer group parametersParameter
|
Description
@@ -16,7 +16,8 @@
|
|---|
Consumer Group Name
|
Name of the consumer group.
-A consumer group must meet the following requirements: - Contains 3 to 64 characters.
- Contains only letters, digits, percent signs (%), vertical bars (|), hyphens (-), and underscores (_).
+ A consumer group must meet the following requirements: - Contains 3 to 64 characters.
- Contains only letters, digits, percent signs (%), vertical bars (|), hyphens (-), and underscores (_).
A percent (%) or vertical bar (|) contained in a consumer group name will be converted to an underscore (_) by Cloud Eye. For example, if a consumer group name is test%01, it will be displayed as test_01 on Cloud Eye.
+
Once the consumer group is created, you cannot modify its name.
|
@@ -39,6 +40,12 @@
If this option is enabled, consumers consume messages in sequence. Orderly consumption ensures sequential consumption by message sending. In this case, earlier messages are consumed before later messages
|
+Description
+ |
+Description of the consumer group.
+Value range: 0–200 characters.
+ |
+
Viewing RocketMQ Consumer Group Details
After a consumer group is created, you can query its configuration and status on the console.
- Prerequisite- A RocketMQ instance has been created.
- A consumer group has been created.
+
- Viewing RocketMQ Consumer Group Details- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Consumer Groups.
- Click the desired consumer group to go to the consumer group details page.
In the upper part of the page, you can view the consumer group name, the maximum number of retries, orderly consumption, and whether messages are broadcast.
-In the lower part of the page, you can view the consumer group information, all topics subscribed by the consumer group, user permissions, and subscriptions.
+Viewing RocketMQ Consumer Group Details- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Consumer Groups.
- Click the desired consumer group to go to the consumer group details page.
In the upper part of the page, you can view the consumer group name, maximum number of retries, orderly consumption, and whether messages are broadcast.
+In the lower part of the page, you can view the consumer list information, all topics subscribed by the consumer group, user permissions, and subscriptions.
+ The user permission information is displayed only when ACL has been enabled during instance creation or on the overview page of the instance.
+
diff --git a/docs/dms_rocketmq/umn/hrm-ug-015.html b/docs/dms_rocketmq/umn/hrm-ug-015.html
index 9bd52930c..f6bacf730 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-015.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-015.html
@@ -2,10 +2,10 @@
Modifying RocketMQ Consumer Group Configurations
After creating a consumer group, you can modify its configuration as required.
- Prerequisite- A RocketMQ instance has been created.
- A consumer group has been created.
+
- Modifying RocketMQ Consumer Group Configurations- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Consumer Groups.
- Modify consumer group parameters in either of the following ways:
- In the row containing the consumer group whose parameters you want to modify, click Edit.
- Click a consumer group and then click Edit in the upper right corner of the consumer group details page.
+Modifying RocketMQ Consumer Group Configurations- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Consumer Groups.
- Modify consumer group parameters in either of the following ways:
- In the row containing the consumer group whose parameters you want to modify, click Edit.
- Click a consumer group and then click Edit in the upper right corner of the consumer group details page.
- Modify consumer group parameters by referring to Table 1.
Table 1 Consumer group parametersParameter
|
@@ -32,6 +32,12 @@
Orderly consumption ensures sequential consumption by message sending. In this case, earlier messages are consumed before later messages
|---|
+Description
+ |
+Description of the consumer group.
+0–200 characters
+ |
+
Deleting a RocketMQ Consumer Group
If a consumer group is no longer used, delete it by referring to this section.
- Prerequisites- A RocketMQ instance has been created.
- A consumer group has been created.
+
- Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Consumer Groups.
- Delete consumer groups in any of the following ways:
- In the row containing the desired consumer group, click Delete.
- Click a consumer group to go to the consumer group details page and then click Delete in the upper right corner.
- To delete multiple consumer groups at a time, select the consumer groups, and click Delete Consumer Group above the consumer group list.
+Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Consumer Groups.
- Delete consumer groups in any of the following ways:
- In the row containing the desired consumer group, click Delete.
- Click a consumer group to go to the consumer group details page and then click Delete in the upper right corner.
- To delete multiple consumer groups at a time, select the consumer groups, and click Delete Consumer Group above the consumer group list.
- Click OK.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-018.html b/docs/dms_rocketmq/umn/hrm-ug-018.html
index cd039420d..95a58933f 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-018.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-018.html
@@ -18,7 +18,7 @@
Conversion Rule
|
- Monitored Object (Dimension)
+ | Dimension
|
Monitoring Period (Raw Data)
|
@@ -36,7 +36,7 @@
N/A
|
- RocketMQ instance
+ | reliablemq_instance_id
|
1 minute
|
@@ -53,7 +53,7 @@
N/A
|
- RocketMQ instance
+ | reliablemq_instance_id
|
1 minute
|
@@ -72,7 +72,7 @@
N/A
|
- RocketMQ instance
+ | reliablemq_instance_id
|
1 minute
|
@@ -89,7 +89,7 @@
N/A
|
- RocketMQ instance
+ | reliablemq_instance_id
|
1 minute
|
@@ -106,7 +106,7 @@
N/A
|
- RocketMQ instance
+ | reliablemq_instance_id
|
1 minute
|
@@ -122,13 +122,13 @@
Description
|
- Value Range
+ | Value Range
|
- Unit
+ | Unit
|
Conversion Rule
|
- Monitored Object (Dimension)
+ | Dimension
|
Monitoring Period (Raw Data)
|
@@ -140,13 +140,13 @@
Number of messages received by the topic per minute
|
- > 0
+ | > 0
|
- Count
+ | Count
|
N/A
|
- RocketMQ instance queue
+ | reliablemq_instance_id,reliablemq_topics
|
1 minute
|
@@ -157,13 +157,13 @@
Number of messages retrieved from the topic per minute
|
- > 0
+ | > 0
|
- Count
+ | Count
|
N/A
|
- RocketMQ instance queue
+ | reliablemq_instance_id,reliablemq_topics
|
1 minute
|
@@ -174,13 +174,13 @@
Number of messages received by the topic per second
|
- > 0
+ | > 0
|
- Count/s
+ | Count/s
|
N/A
|
- RocketMQ instance queue
+ | reliablemq_instance_id,reliablemq_topics
|
1 minute
|
@@ -191,13 +191,13 @@
Number of messages retrieved from the topic per second
|
- > 0
+ | > 0
|
- Count/s
+ | Count/s
|
N/A
|
- RocketMQ instance queue
+ | reliablemq_instance_id,reliablemq_topics
|
1 minute
|
@@ -208,13 +208,13 @@
Message creation traffic of the topic
|
- ≥ 0
+ | ≥ 0
|
- Byte/s
+ | Byte/s
|
1024(IEC)
|
- RocketMQ instance queue
+ | reliablemq_instance_id,reliablemq_topics
|
1 minute
|
@@ -225,13 +225,13 @@
Message retrieval traffic of the topic
|
- ≥ 0
+ | ≥ 0
|
- Byte/s
+ | Byte/s
|
1024(IEC)
|
- RocketMQ instance queue
+ | reliablemq_instance_id,reliablemq_topics
|
1 minute
|
@@ -253,7 +253,7 @@
Conversion Rule
|
- Monitored Object (Dimension)
+ | Dimension
|
Monitoring Period (Raw Data)
|
@@ -273,7 +273,7 @@
N/A
|
- Consumer group of a RocketMQ instance
+ | reliablemq_instance_id,reliablemq_groups
|
1 minute
|
@@ -293,7 +293,7 @@
N/A
|
- Consumer group of a RocketMQ instance
+ | reliablemq_instance_id,reliablemq_groups
|
1 minute
|
@@ -312,7 +312,7 @@
N/A
|
- Consumer group of a RocketMQ instance
+ | reliablemq_instance_id,reliablemq_groups,reliablemq_groups_topics
|
1 minute
|
@@ -331,7 +331,7 @@
N/A
|
- Consumer group of a RocketMQ instance
+ | reliablemq_instance_id,reliablemq_groups,reliablemq_groups_topics
|
1 minute
|
@@ -350,7 +350,7 @@
N/A
|
- Consumer group of a RocketMQ instance
+ | reliablemq_instance_id,reliablemq_groups,reliablemq_groups_topics
|
1 minute
|
@@ -390,7 +390,7 @@
N/A
|
- Dead letter queue of a RocketMQ instance
+ | reliablemq_instance_id,reliablemq_dlq_topics
|
1 minute
|
@@ -398,8 +398,24 @@
|---|
If a monitored object has multiple dimensions, the dimensional level of specific metrics is required when you use APIs to query the metrics.
+For example, to query the number of accumulated messages (group_accumulation) of a consumer group, its dimension is "reliablemq_instance_id,reliablemq_groups", indicating that reliablemq_instance_id is numbered 0 and reliablemq_groups is numbered 1.
+- To query a single metric by calling the API, the reliablemq_groups dimension is used as follows:
dim.0=reliablemq_instance_id,6a0df74a-fxxx-497bfdda6c8e&dim.1=reliablemq_groups,10
+6a0df74a-fxxx-497bfdda6c8e and 10 are the dimension values of reliablemq_instance_id and reliablemq_groups. For details about how to obtain them, see the guide in the Dimension table.
+ - To batch query metrics by calling the API, the reliablemq_groups dimension is used as follows:
"dimensions": [
+ {
+ "name": "reliablemq_instance_id",
+ "value": "6a0df74a-fxxx-497bfdda6c8e"
+ },
+ {
+ "name": "reliablemq_groups",
+ "value": "10"
+ }
+ ]
+6a0df74a-fxxx-497bfdda6c8e and 10 are the dimension values of reliablemq_instance_id and reliablemq_groups. For details about how to obtain them, see the guide in the Dimension table.
+
Dimensions
+ Dimensions
Key
|
Value
@@ -408,27 +424,27 @@
|
|---|
reliablemq_instance_id
|
-RocketMQ instance
+ | RocketMQ instance ID, for example, 6a0df74a-fxxx-497bfdda6c8e.
|
reliablemq_topics
|
-RocketMQ instance queue
+ | Topic name, for example, topic-01.
|
reliablemq_groups
|
-Consumer group of a RocketMQ instance
+ | RocketMQ instance consumer group, for example, group-01.
|
reliablemq_groups_topics
|
-Consumer group of a RocketMQ instance queue
+ | Name of the topic consumed, for example, topic-01.
|
reliablemq_dlq_topics
|
-Dead letter queue of a RocketMQ instance
+ | Name of the dead letter queue of the RocketMQ instance, for example, DLQ_group-1.
|
diff --git a/docs/dms_rocketmq/umn/hrm-ug-019.html b/docs/dms_rocketmq/umn/hrm-ug-019.html
index abd1eac90..e21a708cd 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-019.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-019.html
@@ -2,11 +2,11 @@
Viewing RocketMQ Monitoring Metrics
Cloud Eye monitors RocketMQ instance metrics in real time. You can view these metrics on the console.
- PrerequisitesA RocketMQ instance has been created.
+ PrerequisiteA RocketMQ instance has been created.
- Viewing RocketMQ Metrics- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- Choose Monitoring in the navigation pane.
- View monitoring data by the instance, topics, consumer groups, and dead letter queues.
- (Optional) Click View details on the By Instance, By Topic, By Consumer Group, or By Dead Letter Queue tab page to go to the Cloud Eye console.
On the instance list page, you can also click View Metric in the row containing the desired instance to go to the Cloud Eye console.
-On the Cloud Eye console, you can select metrics and rearrange their order.
+Viewing RocketMQ Metrics- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- View the instance metrics in any of the following ways:
- View all monitoring data: After a RocketMQ instance name, click View Metric. On the Cloud Eye console, view the metrics. Metric data is reported to Cloud Eye every minute.
- View all monitoring data: Click a RocketMQ instance name to go to the instance overview page. In the navigation pane, choose Monitoring. On the displayed page, view the monitoring data. The data is updated every minute.
+ - View monitoring data by the instance, topics, consumer groups, and dead letter queues.
- (Optional) Click View details on the By Instance, By Topic, By Consumer Group, or By Dead Letter Queue tab page to go to the Cloud Eye console.
On the Cloud Eye console, you can select metrics and rearrange their order.
For example, if you only need to view the Created Messages and Retrieved Messages metrics on the By Instance tab page, do as follows:
- On the By Instance tab page, click Select Metric.
- Select Created Messages and Retrieved Messages, and click OK.
- Drag and drop the selected metrics to desired locations to rearrange the order.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-023.html b/docs/dms_rocketmq/umn/hrm-ug-023.html
index b74036001..3c7b52048 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-023.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-023.html
@@ -3,67 +3,56 @@
Managing RocketMQ Dead Letters
When a message fails to be consumed and retried, RocketMQ does not discard it immediately, but forwards it to a specific dead letter queue. Messages in such a queue are dead letter messages. These messages can be redelivered and consumed again after faults are rectified. If they cannot be processed temporarily, they can be exported and saved in case of deletion after expiration.
Prerequisites- A RocketMQ instance and consumer groups have been created.
- To query messages by message ID, you need the name of the consumer group to which the message belongs and the message ID.
Message ID is the MsgId returned after the message is produced, for example, the content returned in 6. Message IDs can be recorded in topic queries.
- - To query messages by message key, you need the name of the consumer group to which the message belongs and the message key.
Message Key is the message key configured in 7. Message keys can be recorded in topic queries.
+ - To query messages by message key, you need the name of the consumer group to which the message belongs and the message key.
The message key is configured in 7. Message keys can be recorded in topic queries.
How to Query Dead Letter MessagesTable 1 compares three query modes.
- Table 1 Dead letter message query modesSearch By
+Table 1 Dead letter message query modesSearch By
|
-Search With
+ | Search With
|
-Search In
- |
-Description
+ | Description
|
|---|
-Group
+ | Group
|
-Group and time range
+ | Group and time range
|
-Range
- |
-Based on a consumer group and time range, you can obtain all the dead letter messages meeting the query criteria in batches. Due to the large number of messages, matching is more difficult.
+ | Based on a consumer group and time range, you can obtain all the dead letter messages meeting the query criteria in batches. Due to the large number of messages, matching is more difficult.
|
-Message ID
+ | Message ID
|
-Group and message ID
+ | Group and message ID
|
-Exact mode
- |
-Based on a consumer group and message ID, you can accurately locate a dead letter message to obtain its attributes.
+ | Based on a consumer group and message ID, you can accurately locate a dead letter message to obtain its attributes.
|
-Message key
+ | Message key
|
-Group and message key
+ | Group and message key
|
-Fuzzy mode
- |
-Dead letter messages that contain specific keys can be queried by consumer group and message key.
+ | Dead letter messages that contain specific keys can be queried by consumer group and message key.
|
Querying Dead Letter Messages- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Dead Letter Queues.
- Query dead letter messages in either of the following ways:
- By group: Select the name of the consumer group to be queried from the Consumer Group drop-down list. For Stored, select a time period.
-
- By message ID: Select the name of the consumer group to be queried from the Consumer Group drop-down list, enter the message ID of the dead letter message to be queried, and click Search.
-
- By message key: Select the name of the consumer group to be queried from the Consumer Group drop-down list, enter the message key of the dead letter message to be queried, and click Search.
-
+Querying Dead Letter Messages- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Dead Letter Queues.
- Query dead letter messages in either of the following ways:
- By group: Select the name of the consumer group to be queried from the Consumer Group drop-down list. For Stored, select a time period.
- By message ID: Select the name of the consumer group to be queried from the Consumer Group drop-down list, enter the message ID of the dead letter message to be queried, and click Search.
- By message key: Select the name of the consumer group to be queried from the Consumer Group drop-down list, enter the message key of the dead letter message to be queried, and click Search.
Resending a Dead Letter MessageMessages that cannot be properly processed (consumption exception or return failure) will be in dead letter queues. They can be redelivered to consumers in the dead letter queues on the console.
- - Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Dead Letter Queues.
- Resend dead letter messages in either of the following ways:
After a dead letter message is successfully resent, it still exists in the dead letter queue and will not be deleted. Do not retry resending a dead letter message to avoid repeated consumption.
+- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Dead Letter Queues.
- Resend dead letter messages in either of the following ways:
After a dead letter message is successfully resent, it still exists in the dead letter queue and will not be deleted. Do not retry resending a dead letter message to avoid repeated consumption.
- In the row containing the dead letter message to be resent, click Resend.
- Select multiple dead letter messages to be resent and click Resend.
Exporting Dead Letter Messages- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Dead Letter Queues.
- Click Export Message in the row containing the desired message.
The message will be exported in JSON format.
+Exporting Dead Letter Messages- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Dead Letter Queues.
- Click Export Message in the row containing the desired message.
The message will be exported in JSON format.
To export multiple dead letter messages at a time, select them and click Export Message above the message list.
Table 2 describes the fields of an exported message.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-026.html b/docs/dms_rocketmq/umn/hrm-ug-026.html
index bba865c9a..1ccfc6a28 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-026.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-026.html
@@ -9,7 +9,7 @@
- Changing RocketMQ Message Retention Period
-- Enabling and Querying RocketMQ Message Tracing
+ - Enabling RocketMQ Message Tracing and Querying Traces
- Verifying RocketMQ Message Consumption
diff --git a/docs/dms_rocketmq/umn/hrm-ug-027.html b/docs/dms_rocketmq/umn/hrm-ug-027.html
index b7e72127b..8b8bdceec 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-027.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-027.html
@@ -6,10 +6,10 @@
- Expired files are cleared at 04:00 every day. Earlier instances that do not have a time zone are cleared at 12:00 every day.
- Expired files are deleted immediately when the disk usage reaches 75%.
- The earliest files are deleted, regardless of whether they have expired, when the disk usage reaches 85%.
Prerequisites- A RocketMQ instance and topics have been created.
- To query messages by message ID, you need the name of the topic to which the message belongs and the message ID.
Message ID is the MsgId returned after the message is produced, for example, the content returned in 6. Message IDs can be recorded in topic queries.
- - To query messages by message key, you need the name of the topic to which the message belongs and the message key.
Message Key is the message key configured in 7. Message keys can be recorded in topic queries.
+ - To query messages by message key, you need the name of the topic to which the message belongs and the message key.
The message key is configured in 7. Message keys can be recorded in topic queries.
How to QueryTable 1 compares three modes of query.
+ Query ModesTable 1 compares three modes of query.
Table 1 Message query modesSearch By
|
@@ -44,11 +44,8 @@
|---|
- Querying the Message Content- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Message Query.
- Query messages in either of the following ways:
- By topic: Select the topic to be queried from the Topic drop-down list. For Stored, select a time period.
-
- By message ID: Select the name of the topic to be queried from the Topic drop-down list, enter the ID of the message to be queried, and click Search.
-
- By message key: Select the name of the topic to be queried from the Topic drop-down list, enter the key of the message to be queried, and click Search.
-
+Querying the Message Content- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Message Query.
- Query messages in either of the following ways:
- By topic: Select the topic to be queried from the Topic drop-down list. For Stored, select a time period.
- By message ID: Select the name of the topic to be queried from the Topic drop-down list, enter the ID of the message to be queried, and click Search.
- By message key: Select the name of the topic to be queried from the Topic drop-down list, enter the key of the message to be queried, and click Search.
- In the row that contains the desired message, click View Details to view the message content.
The message details include the message size, message creation time, and message content. - If the message body is greater than 4096 bytes, some content may not be displayed on the console. In this case, click Download to view the message body in the downloaded JSON file.
- Click Copy to copy the message content.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-028.html b/docs/dms_rocketmq/umn/hrm-ug-028.html
index 6bc27b23a..a36a8d713 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-028.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-028.html
@@ -1,9 +1,9 @@
- Enabling and Querying RocketMQ Message Tracing
- Message traces contain complete time and location information during production and consumption of a message. Message tracing enables diagnosis of real messaging status when exceptions (e.g., production and consumption failures) occur. Message traces can be queried by message ID, message key, or topic time range.
- The following procedures describe how to enable and query message tracing in Java, Go, and Spring.
- PrerequisitesTransactional message tracing is available only for Java 4.9.0 and later producers. For RocketMQ instances with SSL enabled, message tracing is available only for Java 4.9.2 and later producers and consumers.
+ Enabling RocketMQ Message Tracing and Querying Traces
+ Message traces contain complete time and location information during production and consumption of a message. Message tracing enables diagnosis of messaging status when exceptions (e.g., production and consumption failures) occur. Message traces can be queried by message ID, message key, or topic time range.
+ The following procedures describe how to enable message tracing in Java, Go, and Spring and how to query traces.
+ PrerequisitesTransactional message tracing is available only for Java 4.9.0 and later producers. For RocketMQ instances with SSL enabled, both the producer and consumer must be Java 4.9.2 and later.
Enabling RocketMQ Message Tracing (Java)Do as follows to enable message tracing on clients:
- Enabling message tracing on a producer client (tracing messages other than transactional messages)
Set enableMsgTrace of the constructor to true. For example:
@@ -69,7 +69,7 @@ func main() {
fmt.Printf("shutdown producer error: %s", err.Error())
}
}
-192.168.0.1:8100 is the connection address and port of the RocketMQ instance. Obtain yours from Basic Information > Connection on the RocketMQ console.
+192.168.0.1:8100 is the connection address and port of the RocketMQ instance. Obtain yours from Overview > Connection on the RocketMQ console.
- Enable message tracing on the consumer. Replace the information in bold with the actual values.
package main
import (
@@ -131,21 +131,21 @@ func main() {
Connection address and port of the RocketMQ instance
|
-Basic Information > Connection page on the RocketMQ console.
+ | Overview > Connection on the RocketMQ console.
|
|
|---|
testGroup
|
Name of the consumer group created in the RocketMQ instance
|
-Consumer Groups page on the RocketMQ console.
+ | Instance > Consumer Groups page on the RocketMQ console.
|
TopicTest
|
Name of the topic created in the RocketMQ instance
|
-Topics page on the RocketMQ console.
+ | Instance > Topics page on the RocketMQ console.
|
@@ -170,11 +170,8 @@ public class MyConsumer implements RocketMQListener<String> {
For more information, see Message Tracing. To configure parameter accessChannel, use the default value LOCAL.
-Viewing the Message Trace- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Message Query.
- Query messages in either of the following ways:
- By topic: Select the topic to be queried from the Topic drop-down list. For Stored, select a time period.
-
- By message ID: Select the name of the topic to be queried from the Topic drop-down list, enter the ID of the message to be queried, and click Search.
-
- By message key: Select the name of the topic to be queried from the Topic drop-down list, enter the key of the message to be queried, and click Search.
-
+Viewing the Message Trace- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Message Query.
- Query messages in either of the following ways:
- By topic: Select the topic to be queried from the Topic drop-down list. For Stored, select a time period.
- By message ID: Select the name of the topic to be queried from the Topic drop-down list, enter the ID of the message to be queried, and click Search.
- By message key: Select the name of the topic to be queried from the Topic drop-down list, enter the key of the message to be queried, and click Search.
- Locate the row containing the message to be queried. Click View Message Trace.
- View the message trace to check whether the message is successfully produced or consumed.
Table 2 describes message trace parameters.
Table 2 Message trace parametersParameter
@@ -202,8 +199,9 @@ public class MyConsumer implements RocketMQListener<String> {
|
|---|
Consumer status
|
-A consumer can be in one of the following states:
-- Retrieved
- Retrieval timed out
- Abnormal retrieval
- NULL returned
- Retrieval failed
+ | Status of the consumer.
+The value of this parameter is not fixed. It is the return value set by the customer based on the actual client consumption. Common example values are as follows:
+- Retrieved
- Retrieval timed out
- Retrieval failed
|
Retrieved
diff --git a/docs/dms_rocketmq/umn/hrm-ug-029.html b/docs/dms_rocketmq/umn/hrm-ug-029.html
new file mode 100644
index 000000000..35a9153b8
--- /dev/null
+++ b/docs/dms_rocketmq/umn/hrm-ug-029.html
@@ -0,0 +1,11 @@
+
+
+Permissions Management
+
+
+
diff --git a/docs/dms_rocketmq/umn/hrm-ug-030.html b/docs/dms_rocketmq/umn/hrm-ug-030.html
index d26c66a18..427a2b842 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-030.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-030.html
@@ -5,17 +5,17 @@
- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing DMS for RocketMQ resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust an account or a cloud service to perform efficient O&M on your DMS for RocketMQ resources.
If your account meets your permissions requirements, you can skip this section.
This section describes the procedure for granting user permissions. Figure 1 shows the process flow.
-PrerequisitesLearn about the permissions (see Permissions Management) supported by DMS for RocketMQ and choose policies or roles according to your requirements. For the system policies of other services, see Permissions.
+ PrerequisitesLearn about the permissions (see Permissions Management) supported by DMS for RocketMQ and choose policies or roles according to your requirements. For the system policies of other services, see Permissions.
DMS for RocketMQ permissions policies are based on DMS. Therefore, when assigning permissions, select DMS permissions policies.
- Process FlowFigure 1 Process for granting DMS for RocketMQ permissions
+ Process FlowFigure 1 Process for granting DMS for RocketMQ permissions
- - On the IAM console, create a user group and grant it permissions.
DMS ReadOnlyAccess is used as an example.
+- On the IAM console, create a user group and grant it permissions.
DMS ReadOnlyAccess is used as an example.
- Create an IAM user and add it to the created user group.
- Log in as the IAM user and verify permissions.
In the authorized region, perform the following operations:
-- Choose Service List > Distributed Message Service. Then click Create Instance on the console of DMS for RocketMQ. If a message appears indicating that you have insufficient permissions to perform the operation, the DMS ReadOnlyAccess policy is in effect.
- Choose Service List > Elastic Volume Service. If a message appears indicating that you have insufficient permissions to access the service, the DMS ReadOnlyAccess policy is in effect.
+- Choose Service List > Distributed Message Service for RocketMQ. Then click Create Instance on the console of DMS for RocketMQ. If a message appears indicating that you have insufficient permissions to perform the operation, the DMS ReadOnlyAccess policy is in effect.
- Choose Service List > Elastic Volume Service. If a message appears indicating that you have insufficient permissions to access the service, the DMS ReadOnlyAccess policy is in effect.
- Example Custom PoliciesCustom policies can be created to supplement the system-defined policies of DMS for RocketMQ. For the actions that can be added for custom policies, see Permissions Policies and Supported Actions.
+ Example Custom PoliciesCustom policies can be created to supplement the system-defined policies of DMS for RocketMQ. For the actions that can be added for custom policies, see "Permissions and Supported Actions" in Distributed Message Service for RocketMQ API Reference.
To create a custom policy, choose either visual editor or JSON.
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Create a JSON policy or edit an existing one.
For details, see Creating a Custom Policy. This section lists examples of common DMS for RocketMQ custom policies.
@@ -103,5 +103,16 @@
-
+
+
+
\ No newline at end of file
diff --git a/docs/dms_rocketmq/umn/hrm-ug-033.html b/docs/dms_rocketmq/umn/hrm-ug-033.html
index 0d5ed56e1..abd31191f 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-033.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-033.html
@@ -6,53 +6,51 @@
PrerequisiteYou can change the public access setting only when the RocketMQ instance is in the Running state.
Enabling Public Access- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- Click
 next to Public Access in the Connection area. - Click
 , in the Elastic IP Address area, select IP addresses as prompted, and click  .If no EIP exists in the Elastic IP Address drop-down list box, or the EIPs are insufficient, click Create Elastic IP to create an EIP on the page that is displayed. After the EIP is created, return to the RocketMQ console, click  next to Elastic IP Address, and select the new EIP from the drop-down list.
-
+Enabling Public Access- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- Click next to Public Access in the Connection area.
- Click , in the Elastic IP Address area, select IP addresses as prompted, and click .
If no EIP exists in the Elastic IP Address drop-down list box, or the EIPs are insufficient, click Create Elastic IP to create an EIP on the page that is displayed. After the EIP is created, return to the RocketMQ console, click next to Elastic IP Address, and select the new EIP from the drop-down list.
After public access is enabled, Instance Address (Public Network) and gRPC Connection Address will be displayed for a RocketMQ instance.
-
-Figure 1 Instance Address (Public Network)
+Figure 1 Instance address (public network)
After public access is enabled, modify security group rules before attempting to access the RocketMQ instance.
-Table 1 Security group rulesDirection
+Table 1 Security group rulesDirection
|
-Protocol
+ | Protocol
|
-Port
+ | Port
|
-Source
+ | Source
|
-Description
+ | Description
|
|---|
-Inbound
+ | Inbound
|
-TCP
+ | TCP
|
-8200
+ | 8200
|
-IP address or IP address group of the RocketMQ client
+ | IP address or IP address group of the RocketMQ client
|
-The port is used for public network access to instances using TCP.
+ | The port is used for public network access to instances using TCP.
|
-Inbound
+ | Inbound
|
-TCP
+ | TCP
|
-8081
+ | 8081
|
-The port is used for public network access to instances using gRPC.
+ | The port is used for public network access to instances using gRPC.
|
-Inbound
+ | Inbound
|
-TCP
+ | TCP
|
-10101
+ | 10101
|
-The port is used for public access to service nodes using TCP.
+ | The port is used for public access to service nodes using TCP.
|
@@ -60,8 +58,8 @@
-Disabling Public Access- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- Click next to Public Access in the Connection area.
- Click
 and then  to disable public access.After public access is disabled, modify security group rules before attempting to access the RocketMQ instance over a private network.
+Disabling Public Access- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- Click next to Public Access in the Connection area.
- Click and then to disable public access.
After public access is disabled, modify security group rules before attempting to access the RocketMQ instance over a private network.
Table 2 Security group rulesDirection
|
@@ -82,7 +80,6 @@
8100
|
IP address or IP address group of the RocketMQ client
-
|
The port is used for private network access to instances using TCP.
|
@@ -113,7 +110,7 @@
diff --git a/docs/dms_rocketmq/umn/hrm-ug-035.html b/docs/dms_rocketmq/umn/hrm-ug-035.html
index 7230d6610..523a9635d 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-035.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-035.html
@@ -2,10 +2,10 @@
Configuring RocketMQ ACL Users
To produce and consume messages to RocketMQ instances with ACL enabled, add ACL users. You can create multiple users and assign different topic and consumer group permissions to them.
- Prerequisites- A RocketMQ instance has been created.
- ACL has been enabled.
+
- Creating a User- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- In the navigation pane, choose Instance > Users.
- Click Create User.
- Configure the user's name and other parameters by referring to Table 1.
+ Creating a User- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Users.
- Click Create User.
- Configure the user's name and other parameters by referring to Table 1.
Table 1 User parametersParameter
|
Description
@@ -48,17 +48,17 @@
Accessing the Server as a UserAfter ACL is enabled for an instance, user authentication information must be added to both the producer and consumer configurations. To enable ACL using Java, Go, or Python, refer to the following documents:
- Section "Java" > "Controlling Access with ACL" in Distributed Message Service for RocketMQ Developer Guide
- Section "Go" > "Controlling Access with ACL" in Distributed Message Service for RocketMQ Developer Guide
- Section "Python" > "Controlling Access with ACL" in Distributed Message Service for RocketMQ Developer Guide
Modifying User Information- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- In the navigation pane, choose Instance > Users.
- In the row containing the desired user, click Edit.
- Modify the user information as required.
Usernames cannot be changed. For other parameters, see Table 1.
+Modifying User Information- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Users.
- In the row containing the desired user, click Edit.
- Modify the user information as required.
Usernames cannot be changed. For other parameters, see Table 1.
- Click OK.
Exporting Users- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- In the navigation pane, choose Instance > Users.
- Export the user list in either of the following ways:
- Select the desired users and choose Export > Export selected data to an XLSX file to export specified users.
- Choose Export > Export all data to an XLSX file to export all users.
+Exporting Users- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Users.
- Export the user list in either of the following ways:
- Select the desired users and choose Export > Export selected data to an XLSX file to export specified users.
- Choose Export > Export all data to an XLSX file to export all users.
Deleting a UserDeleting a user will remove its authorization relationship and disconnect it from the instance.
- - Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- In the navigation pane, choose Instance > Users.
- In the row containing the desired user, click Delete.
- Click OK.
+ - Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Users.
- In the row containing the desired user, click Delete.
- Click OK.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-038.html b/docs/dms_rocketmq/umn/hrm-ug-038.html
index 1f3b2e94e..bb019d3b1 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-038.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-038.html
@@ -1,7 +1,7 @@
Modifying RocketMQ Specifications
- After creating a RocketMQ instance, you can increase or decrease its specifications. Table 1 lists available modification options. Only one configuration type can be changed at a time.
+ After creating a RocketMQ instance, you can increase or decrease its specifications. Table 1 lists available modification options. Only one object can be modified at a time.
Table 1 Specification modification optionsModified Object
|
@@ -36,30 +36,28 @@
√
|
-√
+ | √ (Only some flavors can be decreased. See the console.)
|
|---|
- Notes and ConstraintsYou can expand the storage space 20 times.
- ImpactIncreasing the storage space and instance specifications does not affect services.
Prerequisites- The RocketMQ instance is in the Running state.
- The user to modify instance specifications must have the DMS FullAccess permission.
- Expanding the Storage Space- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Modify the instance specifications in either of the following ways:
- Locate the row containing the desired instance, choose Modify Specifications.
- Click a RocketMQ instance to go to the instance details page. In the upper right corner, click Modify Specifications.
- - Select Storage for Change By and enter a storage size.
- Click Next.
- Confirm the configurations and click Submit.
- Click Back to DMS (for RocketMQ) List. The instance is in the Changing state.
When the instance is in the Running state, the expanded available storage space can be viewed in Used/Available Storage Space.
+Expanding the Storage Space- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Modify the instance specifications in either of the following ways:
- Locate the row containing the desired instance, choose Modify Specifications.
- Click a RocketMQ instance name to go to the instance overview page. In the upper right corner, click Modify Specifications.
+ - Select Storage for Change By and enter a storage size.
- Click Next.
- Confirm the information. If Billing Mode is Yearly/Monthly, click Pay Now. If Billing Mode is Pay-per-use, click Submit.
- The instance is in the Changing state on the RocketMQ instance list page.
When the instance is in the Running state, the expanded available storage space can be viewed in Used/Available Storage Space.
Available storage space = Actual storage space – Storage space for storing logs – Disk formatting loss
For example, if the storage space is expanded to 700 GB, the storage space for storing logs is 100 GB, and the disk formatting loss is 7 GB, then the available storage space after capacity expansion will be 593 GB.
Increasing an Instance FlavorBefore scaling the instance, ensure that the subnet segments are allowed in the security group.
- - Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Modify the instance specifications in either of the following ways:
- Locate the row containing the desired instance, choose Modify Specifications.
- Click a RocketMQ instance to go to the instance details page. In the upper right corner, click Modify Specifications.
- - Select Flavor for Change By and select a new instance flavor.
- Click Next.
- Confirm the configurations and click Submit.
- Click Back to DMS (for RocketMQ) List. The instance is in the Changing state.
When the instance is in the Running state, view the new instance flavor in Flavor.
+- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Modify the instance specifications in either of the following ways:
- Locate the row containing the desired instance, choose Modify Specifications.
- Click a RocketMQ instance name to go to the instance overview page. In the upper right corner, click Modify Specifications.
+ - Select Flavor for Change By and select a new instance flavor.
- Click Next.
- Confirm the information. If Billing Mode is Yearly/Monthly, click Pay Now. If Billing Mode is Pay-per-use, click Submit.
- The instance is in the Changing state on the RocketMQ instance list page.
When the instance is in the Running state, view the new instance flavor in Flavor.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-039.html b/docs/dms_rocketmq/umn/hrm-ug-039.html
index ec6b84d80..06265c7fa 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-039.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-039.html
@@ -1,17 +1,17 @@
Accessing RocketMQ on a Client (Without SSL)
- This document describes how to access a RocketMQ instance with SSL disabled on the Linux CLI. When SSL is disabled, data is transmitted in plaintext between a client and a RocketMQ instance at high performance.
- Prerequisites- A RocketMQ instance with PLAINTEXT or PERMISSIVE for encryption has been created.
- The network between the client and the RocketMQ instance has been established. For details about network requirements, see RocketMQ Network Connection Conditions.
- A RocketMQ instance has been created and its connection address has been obtained.
The connection address can be obtained from Basic Information > Connection on the RocketMQ console. - If the client uses TCP, obtain Instance Address (Private Network) or Instance Address (Public Network).
- If the client uses gPRC, obtain gRPC Connection Address or gRPC Connection Address (Public Network).
+ This document describes how to access a RocketMQ instance with SSL disabled on the Linux CLI. When SSL is disabled, data is transmitted in plaintext between the client and the RocketMQ instance with high performance.
+ Prerequisites- A RocketMQ instance with PLAINTEXT or PERMISSIVE encryption has been created.
- The network between the client and the RocketMQ instance has been established. For details about network requirements, see RocketMQ Network Connection Conditions.
- You have obtained the RocketMQ instance connection address.
The connection address can be obtained from Overview > Connection on the RocketMQ console. - If the client uses TCP, obtain Instance Address (Private Network) IPv4 or Instance Address (Public Network).
- If the client uses gRPC, obtain gRPC Connection Address IPv4 or gRPC Connection Address (Public Network).
- Security group rules have been configured.
- A topic has been created. The topic name has been obtained and publish and subscribe permissions are granted.
- Java Development Kit 1.8.111 or later has been installed on the client server, and related environment variables have been configured.
- The client server must be able to access the Internet to download the sample software package.
- Accessing the Instance with CLI- Log in to the client server using SSH.
- Download the rocketmq-tutorial software package.
wget https://dms-demos.obs.eu-de.otc.t-systems.com/rocketmq-tutorial.zip
+Accessing the Instance with CLI- Log in to the client server using SSH.
- Download the rocketmq-tutorial software package.
wget https://dms-demo.obs.eu-de.otc.t-systems.com/rocketmq-tutorial.zip
- Decompress the rocketmq-tutorial package.
unzip rocketmq-tutorial.zip
- (Optional) If ACL is enabled for the RocketMQ instance, authentication is required when you run the mqadmin command.
Switch to the directory where the decompressed software package is stored and add the following content to the conf/tools.yml file: accessKey:*******
secretKey:*******
accessKey and secretKey are the username and secret key set on the Users page of the console. For details, see Creating a User.
+accessKey and secretKey are the username and secret key set on the Instance > Users page of the console. For details, see Creating a User.
- Go to the rocketmq-tutorial/bin directory.
cd rocketmq-tutorial/bin
- Produce normal messages using the sample project.
sh mqadmin sendMessage -n "${Connection address}" -t ${Topic name} -p "Message content"
@@ -63,7 +63,7 @@ secretKey:*******
sh mqadmin sendMessage -n "11.xxx.xxx.89:8200;11.xxx.xxx.144:8200" -t topic-test -p "hello rocketmq" -m true
The message is produced when the information in the red box shown in the following figure is displayed.
- - Retrieve messages and send the message traces using the sample project.
sh mqadmin consumeMessage -n "${Connection addresses}" -t ${Topic name} -m true
+ - Consume messages and send the message traces using the sample project.
sh mqadmin consumeMessage -n "${Connection addresses}" -t ${Topic name} -m true
Run the following command with the values obtained in Table 1 to consume messages with traces:
sh mqadmin consumeMessage -n "11.xxx.xxx.89:8200;11.xxx.xxx.144:8200" -t topic-test -m true
The message is consumed when the information in the red box shown in the following figure is displayed.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-040.html b/docs/dms_rocketmq/umn/hrm-ug-040.html
index 576ec30a0..cea40c5b9 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-040.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-040.html
@@ -1,18 +1,17 @@
Accessing RocketMQ on a Client (With SSL)
-This document describes how to access a RocketMQ instance with SSL enabled on the Linux CLI. When SSL is enabled, data is transmitted in ciphertext between a client and a RocketMQ instance with high security.
- Prerequisites- A RocketMQ instance with SSL or PERMISSIVE for encryption has been created.
- The network between the client and the RocketMQ instance has been established. For details about network requirements, see RocketMQ Network Connection Conditions.
- A RocketMQ instance has been created and its connection address has been obtained.
The connection address can be obtained from Basic Information > Connection on the RocketMQ console. - If the client uses TCP, obtain Instance Address (Private Network) or Instance Address (Public Network).
- If the client uses gPRC, obtain gRPC Connection Address or gRPC Connection Address (Public Network).
+ This document describes how to access a RocketMQ instance with SSL enabled on the Linux CLI. When SSL is enabled, data is transmitted in ciphertext between the client and the RocketMQ instance with high security.
+ Prerequisites- A RocketMQ instance with SSL or PERMISSIVE encryption has been created.
- The network between the client and the RocketMQ instance has been established. For details about network requirements, see RocketMQ Network Connection Conditions.
- You have obtained the RocketMQ instance connection address.
The connection address can be obtained from Overview > Connection on the RocketMQ console. - If the client uses TCP, obtain Instance Address (Private Network) IPv4 or Instance Address (Public Network).
- If the client uses gRPC, obtain gRPC Connection Address IPv4 or gRPC Connection Address (Public Network).
- Security group rules have been configured.
- A topic has been created. The topic name has been obtained and publish and subscribe permissions are granted.
- Java Development Kit 1.8.111 or later has been installed on the client server, and related environment variables have been configured.
- The client server must be able to access the Internet to download the sample software package.
- Accessing the Instance with CLI- Log in to the client server using SSH.
- Download the rocketmq-tutorial software package.
wget https://dms-demos.obs.eu-de.otc.t-systems.com/rocketmq-tutorial.zip
-
+Accessing the Instance with CLI- Log in to the client server using SSH.
- Download the rocketmq-tutorial software package.
wget https://dms-demo.obs.eu-de.otc.t-systems.com/rocketmq-tutorial.zip
- Decompress the rocketmq-tutorial package.
unzip rocketmq-tutorial.zip
- (Optional) If ACL is enabled for the RocketMQ instance, authentication is required when you run the mqadmin command.
Switch to the directory where the decompressed software package is stored and add the following content to the conf/tools.yml file: accessKey:*******
secretKey:*******
accessKey and secretKey are the username and secret key set on the Users page of the console. For details, see Creating a User.
+accessKey and secretKey are the username and secret key set on the Instance > Users page of the console. For details, see Creating a User.
- Go to the rocketmq-tutorial/bin directory.
cd rocketmq-tutorial/bin
- Produce normal messages using the sample project.
JAVA_OPT=-Dtls.enable=true sh mqadmin sendMessage -n "${Connection address}" -t ${Topic name} -p "Message content"
@@ -64,7 +63,7 @@ secretKey:*******
JAVA_OPT=-Dtls.enable=true sh mqadmin sendMessage -n "11.xxx.xxx.89:8200;11.xxx.xxx.144:8200" -t topic-test -p "hello rocketmq" -m true
The message is produced when the information in the red box shown in the following figure is displayed.
- - Retrieve messages and send the message traces using the sample project.
JAVA_OPT=-Dtls.enable=true sh mqadmin consumeMessage -n "${Connection addresses}" -t ${Topic name} -m true
+ - Consume messages and send the message traces using the sample project.
JAVA_OPT=-Dtls.enable=true sh mqadmin consumeMessage -n "${Connection addresses}" -t ${Topic name} -m true
Run the following command with the values obtained in Table 1 to consume messages with traces:
JAVA_OPT=-Dtls.enable=true sh mqadmin consumeMessage -n "11.xxx.xxx.89:8200;11.xxx.xxx.144:8200" -t topic-test -m true
The message is consumed when the information in the red box shown in the following figure is displayed.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-041.html b/docs/dms_rocketmq/umn/hrm-ug-041.html
index 3f8145fdf..68ec2f030 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-041.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-041.html
@@ -1,11 +1,10 @@
Accessing an Instance
-
+
-- Configuring RocketMQ Network Connections
+ - Configuring a RocketMQ Network Connection
- Configuring RocketMQ Access Control
diff --git a/docs/dms_rocketmq/umn/hrm-ug-042.html b/docs/dms_rocketmq/umn/hrm-ug-042.html
index b798eb106..c616ccc6f 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-042.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-042.html
@@ -4,21 +4,20 @@
You can diagnose an instance to quickly locate faults when message consumption is slow or fails.
- Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
- Select a consumer group and click Start Diagnose.
After the diagnosis is complete, a diagnosis record is displayed in the Diagnosis Reports area.
- - Click View to view the diagnosis result.
The result contains the active status, number of consumers, subscription consistency, and message accumulation.
-Figure 1 Diagnosis result
+Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
- Select a consumer group and click Start Diagnose.
After the diagnosis is complete, a diagnosis record is displayed in the Diagnosis Reports area.
+ - Click View to go to the Diagnosis Report to view the diagnosis result.
The result contains the active status, number of consumers, subscription consistency, client ID, consumption type, and message accumulation.
If the consumer group is not online, the diagnosis is successful, but one abnormality is displayed.
+ - (Optional) In the Consumer Connections area, click View in the Operation column to view the diagnosis details.
+ Exporting Diagnosis Records- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
- Export instance diagnosis records in either of the following ways:
- Select the desired records and choose Export > Export selected data to an XLSX file.
- Choose Export > Export all data to an XLSX file to export all the records.
Exporting Diagnosis Records- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
- Export instance diagnosis records in either of the following ways:
- Select the desired records and choose Export > Export selected data to an XLSX file.
- Choose Export > Export all data to an XLSX file to export all the records.
-
- Deleting Diagnosis Records- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
- Use either of the following methods to delete diagnosis records:
- In the row containing the record you want to delete, click Delete.
- Select multiple records you want to delete and click Delete above the record list.
- - In the confirmation dialog box, click Yes.
+ Deleting Diagnosis Records- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane on the left, choose Analysis & Diagnosis > Instance Diagnosis.
- Use either of the following methods to delete diagnosis records:
- In the row containing the record you want to delete, click Delete.
- Select multiple records you want to delete and click Delete above the record list.
+ - In the confirmation dialog box, click OK.
@@ -27,10 +26,3 @@
-
-
\ No newline at end of file
diff --git a/docs/dms_rocketmq/umn/hrm-ug-043.html b/docs/dms_rocketmq/umn/hrm-ug-043.html
index e4490f081..bb2a9f454 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-043.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-043.html
@@ -34,8 +34,8 @@
|
|---|
Configuring RocketMQ Alarms- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- In the row containing the desired instance, click View Metric.
You are redirected to the metric monitoring page on the Cloud Eye console.
+Configuring RocketMQ Alarms- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- In the row containing the desired instance, click View Metric.
You are redirected to the metric monitoring page on the Cloud Eye console.
- Hover the mouse pointer over a metric and click
 to create an alarm rule for the metric.The Create Alarm Rule page is displayed.
- Specify the alarm rule details.
For details, see Creating Alarm Rules.
- Enter the alarm name and description.
- Specify the alarm policy and alarm severity.
- Set the alarm notification configurations. If you enable Alarm Notification, set the validity period, notification object, and trigger condition.
- Click Create.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-049.html b/docs/dms_rocketmq/umn/hrm-ug-049.html
index 48f10bd77..388913e65 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-049.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-049.html
@@ -4,8 +4,8 @@
This section describes how to produce a specified message for a RocketMQ instance to verify service logic.
Prerequisites- A RocketMQ instance is in the Running state.
- A topic has been created and has the publish permission.
- Accessing RocketMQ on the Console to Produce Messages- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Topics.
- Click Produce Message in the row containing the desired topic. The Produce Message dialog box is displayed.
- Enter the message body, key, and tag (Message Key and Message Tag are optional) and click OK.
When a message "Message sent." is displayed in the upper right corner, the message is sent.
+Accessing RocketMQ on the Console to Produce Messages- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Topics.
- Click Produce Message in the row containing the desired topic. The Produce Message dialog box is displayed.
- Enter the message body, key, and tag (Message Key and Message Tag are optional) and click OK.
When a message "Message sent." is displayed in the upper right corner, the message is sent.
Table 1 Message production parametersParameter
|
@@ -21,13 +21,13 @@
|---|
Message Key
|
-If there are spaces, this will be parsed as multiple keys, and cannot be filtered by Message Key in specific message queries.
+ | If there are spaces, the key will be parsed as multiple keys, and cannot be filtered by Message Key in specific message queries.
The value can contain a maximum of 128 characters.
|
Message Tag
|
-Used as message categories in a topic, and used in produced messages.
+ | Categorizes messages in a topic. Messages are produced with tags.
The value can contain a maximum of 128 characters.
|
diff --git a/docs/dms_rocketmq/umn/hrm-ug-050.html b/docs/dms_rocketmq/umn/hrm-ug-050.html
index 71814ef9e..3b545519d 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-050.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-050.html
@@ -4,8 +4,8 @@
Consumption verification is to resend messages to a specified online client to verify that the consumer can receive messages. Consumption verification causes repeated message consumption.
Prerequisites- Consumption can be verified only when an instance is in the Running state.
- Ensure that the client for which consumption is to be verified is online and the consumer has subscribed to the topic whose message is to be resent.
- Verifying RocketMQ Message Consumption- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Message Query.
- Set search criteria on the top of the page.
- In the row that contains the message to be resent, click Verify Consumption. The Verify Consumption dialog box is displayed.
- Set parameters by referring to Table 1.
+ Verifying RocketMQ Message Consumption- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Message Query.
- Set search criteria on the top of the page.
- In the row that contains the message to be resent, click Verify Consumption. The Verify Consumption dialog box is displayed.
- Set parameters by referring to Table 1.
Table 1 Consumption verification parametersParameter
|
Description
diff --git a/docs/dms_rocketmq/umn/hrm-ug-051.html b/docs/dms_rocketmq/umn/hrm-ug-051.html
index 072771483..a9b5a144e 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-051.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-051.html
@@ -2,10 +2,10 @@
Resetting the RocketMQ Consumer Offset
Resetting the RocketMQ consumer offset modifies the consumer position. Consumers consume messages from the modified positions.
- Prerequisites- A RocketMQ instance has been created.
- A topic has been created.
- A consumer group has been created and there are consumers in the group.
+
- Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Consumer Groups.
- In the row containing the desired consumer group, click Reset Consumer Offset.
- Set parameters by referring to Table 1.
+ Resetting Consumer Offset- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Instance > Consumer Groups.
- In the row containing the desired consumer group, click Reset Consumer Offset.
- Set parameters by referring to Table 1.
Table 1 Parameters for resetting the consumer offsetParameter
|
Description
diff --git a/docs/dms_rocketmq/umn/hrm-ug-056.html b/docs/dms_rocketmq/umn/hrm-ug-056.html
index b964a951b..6ea729790 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-056.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-056.html
@@ -8,8 +8,8 @@
- On the Overview tab page, click Download broker definitions to export the metadata.
Figure 1 Exporting metadata
-Step 2: Migrate Metadata on the Console- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Cloud Migration > Metadata Migration.
- Click Create Migration Task.
- Configure the migration task by referring to Table 1.
+ Step 2: Migrate Metadata on the Console- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the navigation pane, choose Cloud Migration > Metadata Migration.
- Click Create Migration Task.
- Configure the migration task by referring to Table 1.
Table 1 Migration task parametersParameter
|
Description
@@ -44,8 +44,7 @@
|
|---|
- Click OK.
After the migration is complete, view Task Status in the migration task list.
-- If Task Status is Complete, all metadata has been successfully migrated.
Produce and consume messages by referring to or to ensure that metadata is available.
- - If Task Status is Failed, some or all metadata fails to be migrated.
Click the migration task name to go to the migration task details page. In the Migration Result area, view the name of the topic or consumer group that fails to be migrated, the failure cause, and the solution.
+- If Task Status is Complete, all metadata has been successfully migrated.
- If Task Status is Failed, some or all metadata fails to be migrated.
Click the migration task name to go to the migration task details page. In the Migration Result area, view the name of the topic or consumer group that fails to be migrated, the failure cause, and the solution.
PrerequisiteA RocketMQ instance has been created.
Adding and Deleting Tags- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click an instance name to go to the instance details page.
- In the navigation pane, choose Instance > Tags.
- Perform the following operations as required:
- Add a tag
- Click Edit Tag.
- Click Add Tag to set tags with Tag key and Tag value.
You can repeat this step to add up to 20 tags.
-If you have predefined tags, select predefined tag keys and values, and click Add.
- - Click OK.
- - Delete a tag
- Click Edit Tag.
- Click Delete next to the tag to be deleted.
- Click OK.
-
+Configuring Tags for a RocketMQ Instance- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Configure RocketMQ instance tags on the Edit Tag page in any of the following ways:
- In the row containing the desired RocketMQ instance, choose More > Edit Tag.
- Click a RocketMQ instance name to go to the instance overview page. In the navigation pane, choose Instance > Tags.
- Click a RocketMQ instance name to go to the instance overview page. In the upper right corner, choose
 > Edit Tag.
+ - Add, edit, or delete tags as required.
+ Table 2 Tag operationsOperation
+ |
+Procedure
+ |
+
|---|
+
+Adding a tag
+ |
+- Click Add Tag to set tags with Tag key and Tag value. If you have predefined tags, select a predefined pair of tag key and value, and click Add.
A maximum of 20 tags can be added.
+ - Click OK.
View the new tag on the Edit Tag or tag list page.
+
+ |
+
+Editing a tag
+ |
+Modify the tag key and value, and click OK.
+View the edited tag on the Edit Tag or tag list page.
+ |
+
+Deleting a tag
+ |
+In the row containing the tag to be deleted, click Delete. Then, click OK to delete the tag.
+The tags are deleted when they are no longer displayed on the Edit Tag page and tag list.
+ |
+
+
+
+
After creating an instance, you can modify its message retention period based on service requirements. Changing the retention period does not restart the instance. The default message retention period is 48 hours.
PrerequisiteA RocketMQ instance has been created.
Changing RocketMQ Message Retention Period- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- Click next to Message Retention.
Enter an integer in the range from 1 to 720.
+Changing RocketMQ Message Retention Period- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- Click next to Message Retention.
Enter an integer in the range from 1 to 720.
- Click
 . The modification result is displayed in the upper right corner of the page.
You can export a list of instances on the RocketMQ console.
PrerequisiteA RocketMQ instance has been created.
- Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Export the instance list in either of the following ways:
- Select the desired instances and choose Export > Export selected data to an XLSX file to export specified instances.
- Choose Export > Export all data to an XLSX file to export all instances.
+Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Export the instance list in either of the following ways:
- Select the desired instances and choose Export > Export selected data to an XLSX file to export specified instances.
- Choose Export > Export all data to an XLSX file to export all instances.
diff --git a/docs/dms_rocketmq/umn/hrm-ug-061.html b/docs/dms_rocketmq/umn/hrm-ug-061.html
index 675893301..318d4f969 100644
--- a/docs/dms_rocketmq/umn/hrm-ug-061.html
+++ b/docs/dms_rocketmq/umn/hrm-ug-061.html
@@ -46,8 +46,8 @@
PrerequisiteYou can change the access mode of a RocketMQ instance only when the instance is in the Running state.
Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance name to go to the instance details page.
- In the Connection area, specify SSL option. The Confirm dialog box is displayed.
- Click OK. The Background Tasks page is displayed.
If the SSL change task is in the Successful state, the instance access mode is changed successfully.
+Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
+ - Click and choose Application > Distributed Message Service for RocketMQ to open the DMS for RocketMQ page.
- Click a RocketMQ instance name to go to the instance overview page.
- In the Connection area, specify SSL option. The Confirm dialog box is displayed.
- Click OK. The Background Tasks page is displayed.
If the SSL change task is in the Successful state, the instance access mode is changed successfully.
| - Expands the storage space.
- Increases the instance flavor.
|
|---|
-Deleting ConsumerGroup in Batches
+ | Deleting Consumer Group in Batches
|
Deletes multiple consumer groups in batches.
|
@@ -49,9 +49,9 @@
Restarts brokers.
|
-Metadata Migration
+ | Create Migration Task
|
-Migrates metadata.
+ | Creates a metadata migration task.
|
@@ -59,8 +59,8 @@
PrerequisiteA RocketMQ instance has been created.
Procedure- Log in to the console.
- Click in the upper left corner to select a region.
DMS for RocketMQ instances in different regions cannot communicate with each other over an intranet. Select a nearest location for low latency and fast access.
- - Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Click a RocketMQ instance to go to the instance details page.
- In the navigation pane, choose Instance > Background Tasks.
- On the Current Tasks or Scheduled Tasks tab page, specify a time range in the upper left corner. The task information in that time range will be displayed.
On the Background Tasks page, you can also do as follows:
|
|---|
|---|
|
|---|
|
|---|
|
|
|---|
|
