All Products
Search
Document Center

:Why do I still receive alerts about message accumulation of a consumer group after I delete the consumer group?

Last Updated:Nov 19, 2021

Problem description

If you use Message Queue for Apache Kafka whose broker version is 0.10.2, you still receive alerts about message accumulation of a consumer group after you delete the consumer group.

Cause

2.0 previous Kafka server versions, open-source Kafka does not provide an OpenAPI for deleting groups and consumer offset. Therefore, deleting consumer groups is only logically deleted from the console, and does not actually delete information such as consumer offset. Alerts about message accumulation are generated and handled based on consumer offsets. Therefore, you still receive alerts about message accumulation of the consumer group.

Solution

If you do not want to receive alerts about message accumulation of a consumer group after you delete the consumer group, you can use one of the following solutions:

  • Upgrade the broker version of your Message Queue for Apache Kafka instance to 2.2.0 or later. Create a consumer group with the same configuration as that of the consumer group you deleted. Then, delete the created consumer group. For more information about how to upgrade the broker version, see Upgrade the version of an instance.
  • Disable alert rules for message accumulation. For more information about how to disable alert rules for message accumulation, see Monitoring and alerting.
  • Wait for the consumer offset to expire. After the retention period of the consumer offset elapses, the consumer offset expires. In Message Queue for Apache Kafka, consumer offsets are stored in a built-in topic and cannot be directly deleted. If the consumer offset of the consumer group is not updated after the retention period of the consumer offset elapses, the consumer offset is automatically deleted due to expiration. For more information about how to configure the retention period of consumer offset, see Change message configurations.
    Note: If any consumer thread exists in a group, the consumer offset is not deleted even if the consumer offset in the group exceeds the retention period of the consumer offset. For more information, see Why consumer offset expired but has not been deleted?.

  • Create a new group and reset the consumer offset of each partition to 0 in the console. For more information, see Reset consumer offset.

Applicable scope

  • Message Queue for Apache Kafka