In ApsaraMQ for Kafka, a partition is used to store messages, and each topic consists of one or more partitions. The status of a partition includes the message volume, maximum offset, and minimum offset of the partition. If exceptions such as message accumulation and high disk usage occur in an ApsaraMQ for Kafka cluster, you can view the status of each partition in the cluster to check the message volume on the broker and the consumer progress of each partition to troubleshoot the exceptions.
A topic is created. For more information, see Step 3: Create resources.
Log on to the ApsaraMQ for Kafka console.
In the Resource Distribution section of the Overview page, select the region where the ApsaraMQ for Kafka instance that you want to manage resides.
On the Instances page, click the name of the instance that you want to manage.
In the left-side navigation pane, click Topics.
On the Topics page, find the topic that you want to manage and choose in the Actions column.
Table 1. Information about the status of a partition
The partition ID.
The minimum offset in the partition.
The maximum offset in the partition.
Number of Messages in Partition
The total number of messages in the partition.
Last Updated At
The time when the last message in the partition is stored.
If partitions are unevenly distributed among the topics that use cloud storage in a cluster, you can use the partition balancing and traffic redirection features provided by ApsaraMQ for Kafka to redistribute the partitions or redirect the traffic of a topic. For more information, see Partition balancing and traffic redirection.
If your messages are unevenly distributed among partitions, refer to Why are the messages that are sent to a topic unevenly distributed among the partitions of the topic?
If the values in the Last Updated At column are incorrectly displayed, refer to Why is 1970 or "--" displayed in the Last Updated At column for the partitions of a topic?