Problem description
Partition skew causes high usage of some disks in the cluster and insufficient utilization of disk performance and capacity.
Partition skew also results in excessive traffic in some topics and triggers throttling on a single node.
Possible cause
When you create a topic, the number of partitions is not set to a value that is a multiple of the number recommended by the system.
Solution
Log on to the ApsaraMQ for Kafka console. In the left-side navigation pane, click Instances.
In the top navigation bar, select the region where the 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 page that appears, click the name of the topic that you want to manage.
On the Topic Details page, perform the following steps:
Non-serverless instances
On the Configuration Information tab of the Topic Details page, click Increase Partitions next to the Partitions parameter.
In the Increase Partitions panel, click the upward or downward arrow in the Partitions field to change the number of partitions to a multiple of the recommended number.
NoteIf you cannot increase the number of partitions in a topic that uses cloud storage for business reasons, you can use the partition balancing feature to change the location of the partitions. After you change the location, new data in the partitions is redirected to a disk that has low usage. After messages in the topic expire, the data on the original disk is deleted and disk usage is reduced. For more information, see Partition rebalancing and traffic redirection.
Serverless instances
Click Edit next to the Partition Replicas parameter.
In the Edit Partition Replicas panel, click the upward or downward arrow in the Partition field to change the number of partitions to a multiple of the recommended number.