humkum opened a new issue, #8192: URL: https://github.com/apache/rocketmq/issues/8192
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/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 CentOS7.3 ### RocketMQ version 5.2.0 ### JDK Version Open_JDK 1.8.0_202 ### Describe the Bug When the cluster's master had transferred to another node, the messages stored in old master node, which were already consumed, were return consume status with TrackType.NOT_CONSUME_YET。 No consume lag, the message had been already consumed.  The message already consumed returned consumed status with TrackType.NOT_CONSUME_YET  ### Steps to Reproduce 1. Produce a message to cluster, store to master id with ip1 2. Consume the message produced, make sure there's no 3. Change the cluster's master with ip2 4. Check the message track info ### What Did You Expect to See? The consumed messages' consume status is TrackType.CONSUMED ### What Did You See Instead? The consumed messages' consume status is TrackType.NOT_CONSUME_YET ### Additional Context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
