GenerousMan opened a new issue, #6728:
URL: https://github.com/apache/rocketmq/issues/6728

   ### 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
   
   OS: centOS
   
   ### RocketMQ version
   
   5.1.0
   
   ### JDK Version
   
   _No response_
   
   ### Describe the Bug
   
   The confirmOffset may be set to -1 due to the new connection.
   
   
![image](https://github.com/apache/rocketmq/assets/21073949/dc7f742c-1dcf-4f8d-ac2b-99c73661d49f)
   
   If a connection is inited, but has yet been TRANSFER state, then the 
slaveAckOffset will be -1.
   It will make the newConfirmOffset be a wrong value, which is dangerous.
   
   ### Steps to Reproduce
   
   add a log, then you will see the confirmOffset may be -1 value.
   
   ### What Did You Expect to See?
   
   Compute the confirmOffset without those new connections.
   
   ### What Did You See Instead?
   
   The confirmOffset was set to -1.
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to