Scenario Description
RocketMQ instances are an independent running environment in the RocketMQ message queue system and contain independent configuration information, namespaces, topics, and consumer groups. A RocketMQ instance runs independently and can receive, store, and deliver messages. Each RocketMQ instance can be configured with multiple topics, and each topic can be consumed by multiple consumer groups. You can process business separately and concurrently among different business scenarios by configuring instances.
After an instance is successfully created, log in to the Console. The homepage will display a list of instances that can be managed by the user. .
Instance List
1. In the Console, you can view the list of purchased instances. If the list is empty, click Create Instance in the upper right corner to enter the purchase page. For details on creating an instance, see Specific Operation Steps.
2. You can query by instance ID and instance name. Select the query field from the drop-down menu and enter the query information. Click Query to show the required instance data. You can also click Refresh to manually synchronize the latest instance data in the background.
3. You can view basic instance information, including instance name, instance ID, status, engine, billing mode, creation time, and expiration time. The following table introduces the instance status:
Status | Description |
Running | The instance is running properly. Instances in this state can provide services. |
Closed | The instance is faulty. |
Changing | The instance specifications are being changed. |
Change failed | The instance specifications fail to be changed. |
Pause | The instance is frozen. You can renew the frozen instance in More. |
Logout | The instance has expired and is shut down. You need to purchase a new instance. |
Instance Details
1. On the instance list, click Manage.
2. On the displayed page, you can view instance details, including basic information, running status, network, endpoint, and global monitoring. The following table introduces the parameters.
Category | Parameter | Description |
Basic Information | Instance Name | An instance name indicates the name of a specific instance created in RocketMQ. It is used to uniquely identify and distinguish between different instances. An instance name typically consists of letters, numbers, and underscores, and contains a maximum of 255 characters. Instance names must be unique for convenient management. |
Instance ID | An instance ID is the unique identifier of an instance created in RocketMQ. It is automatically generated by the system to differentiate different RocketMQ instances. An instance ID is used in the management and operation of RocketMQ instances. For example, it is used to create, delete, and modify instances. An instance ID usually consists of a string of numbers and letters and must be unique in the RocketMQ cluster. | |
Engine Type | Two types of engines, namely RocketMQ and CTGMQ, are available. | |
Disk Size | Disk size selected for the instance when an order is placed. It is usually an integer multiple of 100G. | |
Disk Type | Disk type selected for the instance when an order is placed. The default type is SAS, or you can select a higher I/O disk. | |
Host Specification | Host specification selected for the instance when an order is placed. It displays the number of CPU cores and memory size. For details about host specifications, see Product Specifications. | |
Number of Brokers | The number of broker nodes refers to the number of nodes acting as brokers in a RocketMQ cluster. Each broker node stores messages, handles message transmission and consumer requests and performs other functions. | |
Instance Description | You can fill in the instance remarks as required. | |
Running State | Running State | Current instance running status. The above table describes each state. |
Payment Type | Payment type selected for the instance when it is created. Two billing modes: subscription and pay-as-you-go. | |
Created at | Instance creation time. | |
Expiration at | Expiration time of subscription-based instances. It is not displayed for pay-as-you-go instances. | |
Network | VPC | The VPC name bound when creating an instance. For details, refer to Preparation Before Ordering. |
Subnet | The subnet name bound when creating an instance. For details, refer to Preparation Before Ordering. | |
Security Group | The security group name bound when creating an instance. For details, refer to Preparation Before Ordering. | |
Endpoint | Client Protocol | The RocketMQ client protocol refers to the protocol specification used for communication and interaction between the applications relying on RocketMQ message queues and the RocketMQ server. |
Network | VPC | |
Endpoint | Specific VPC intranet IP of the endpoint. | |
Global Monitoring | TPS Monitoring | Identify the time curves of production and consumption TPS (2 minutes) for all topics under all brokers in a cluster |
Traffic Monitoring | Identify the accumulated messages of all topics in a cluster. It lists the topics with the top 20 largest number of accumulated messages in reverse order. | |
Global Accumulation | Global accumulation refers to the accumulation of messages in the message queue system. | |
Global Messages | Identify the production status of all topics in a cluster, which ranks in reverse order of existing message sizes. |