ApsaraMQ for Kafka deletes groups asynchronously. A deletion typically completes in 1 to 2 minutes. If a group stays in the Deleting state longer than expected, active consumers are blocking the deletion.
Symptoms
After you delete a group on the Groups page in the ApsaraMQ for Kafka console, the group is in the Deleting state for a long time.
Causes
A group cannot be deleted while either of the following conditions exists:
Active subscriptions. At least one consumer is still subscribed to a topic through this group. The broker cannot remove a group that has active subscriptions.
In-progress consumer offset commits. One or more consumer threads in the group are still committing consumer offsets. The broker waits for all offset commits to finish before it removes the group.
Solution
Step 1: Check for active subscriptions
Log on to the ApsaraMQ for Kafka console.
On the Groups page, locate the group that is stuck in the Deleting state.
Check the subscription and consumer thread status. For more information, see View consumption details.
Step 2: Cancel the subscription and retry the deletion
If the group subscribes to a topic, or any consumer thread is still committing consumer offsets, cancel the subscription.
Wait for the active subscriptions to clear and the consumer offset commits to complete.
Delete the group again from the Groups page.
If the group remains in the Deleting state after all consumers disconnect, retry the deletion from the Groups page.