Why Do Certain Partitions Have Persistent Message Backlogs?
Those partitions have been continuously producing messages, but consumers have not consumed messages from them. As a result, they have persistent data backlogs.
If you encounter a situation where messages from certain partitions are not consumed, you can try to resolve the issue by restarting the client. If the issue can be resolved after a restart, investigate client logs first. You can also submit a ticket for assistance. Insufficient consumers in the consumer group or too slow consumption results in data backlogs.
You can try to increase the number of consumers to accelerate consumption.
The consumer program has a bug that may cause it not to consume messages from certain partitions.
At this point, you need to check the local logs on the consumer for any abnormal information first.