bxfjb opened a new issue, #7790: URL: https://github.com/apache/rocketmq/issues/7790
### 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 CentOS Linux release 7.3.1611 ### RocketMQ version 4.8.0 ### JDK Version 1.8 ### Describe the Bug In dledger mode, master broker which was shut down and reboot would not synchornize consume offset with the previous temporary master broker. The problem described may caused repeatedly consumption. After reading code, one bug may exist in the synchornize logic: BrokerController.java:  The oneway flag is set true, which means that following code in BrokerOuterAPI@registerBrokerAll will return null without waiting for the result:  which caused the following marked code didn't run actually:  Masteraddr which is null leads to a result that SlaveSynchronize@syncAll didnt't run either, including function body of SlaveSynchronize@syncConsumerOffset:  The Synchronization task was set to run every 10 seconds , but before next sync happens, the reboot broker was elected to be master again already, which means it stopped to try to get the newest consume offset, but start to push messsages from the offset before.  ### Steps to Reproduce * Run a cluster in dledger mode. * Shut down master broker gracefully. * Reboot previous master broker, be sure that consume offset increases during downtime. * Repeat consumption should be observed. ### What Did You Expect to See? Rebooted broker should synchornize the newest consume offset and consume from it correctly. ### What Did You See Instead? Abnormal repeated consumption. ### 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
