[Enhancement] Check the existence of consumer group in updateConsumerOffset to prevent dirty consumer offsets

[redlsz]

Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Check the existence of consumer group in command updateConsumerOffset. Return SUBSCRIPTION_GROUP_NOT_EXIST if the group has been deleted.

Motivation

In scenarios where consumer group need to be deleted, if deleteSubscriptionGroup admin is called before shutting down the online consumer clients, the consumer offset records, which is dirty, might be kept in broker. This could raise some problems, such as getting incorrect data when calling queryTopicConsumeByWho.

This is not the good way to use rmq, but it would occur, and be uncontrollable to broker.

Describe the Solution You'd Like

Check the existence of consumer group in command updateConsumerOffset. Return SUBSCRIPTION_GROUP_NOT_EXIST if the group has been deleted.

Describe Alternatives You've Considered

/

Additional Context

No response