rocketmq icon indicating copy to clipboard operation
rocketmq copied to clipboard

[Bug] The consumption offset data of the subscription group cannot be deleted synchronously on the standby node.

Open frinda opened this issue 2 years ago • 1 comments

Before Creating the Bug Report

  • [X] I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • [X] I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

SUSE Linux Enterprise Server 12 SP5

RocketMQ version

develop|4.9.x

JDK Version

JDK 1.8.0_372

Describe the Bug

In active/standby mode, when I run the mqadmin deleteSubGroup -b xxx -g xxx -r true command to delete a subscribed consumer group, the -r parameter is set to true, indicating that the message offset data of the subscribed consumer group is deleted synchronously, but the consumption offset data of the subscribed consumer group on the standby node cannot be deleted synchronously.

Steps to Reproduce

  1. Deploying the active/standby Mode Environment
  2. Send and consume messages with the topic test001 and group 'groupb' in push mode at the same time, run a while(About two or five minutes)
  3. stop producer and consumer, run command ‘mqadmin deleteSubGroup -b xxx -g groupb -r true’ to delete the subscribed consumer group

What Did You Expect to See?

The persistent group consumption offset of topic ‘test001’ on the standby node is deleted, which is the same as that on the active node. image

What Did You See Instead?

The persistent group consumption offset of topic ‘test001’ still exists on the standby node. image

Additional Context

No response

frinda avatar Aug 26 '23 08:08 frinda

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

github-actions[bot] avatar Aug 28 '24 00:08 github-actions[bot]

This issue was closed because it has been inactive for 3 days since being marked as stale.

github-actions[bot] avatar Sep 01 '24 00:09 github-actions[bot]