You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
mac, windows, linux
RocketMQ version
5.1.4
JDK Version
jdk 1.8
Describe the Bug
In controller mode, when a new broker starts, and if it is elected as master, the new broker will keep printing log "Init the confirmOffset", unless you create a topic and send a message to the topic.
Steps to Reproduce
1.set enableControllerMode=true
2.start broker
3.then the broker will keep printing log "Init the confirmOffset" in store.log
What Did You Expect to See?
log "Init the confirmOffset" should't print so frequently
What Did You See Instead?
the broker keeps printing log "Init the confirmOffset"
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
mac, windows, linux
RocketMQ version
5.1.4
JDK Version
jdk 1.8
Describe the Bug
In controller mode, when a new broker starts, and if it is elected as master, the new broker will keep printing log "Init the confirmOffset", unless you create a topic and send a message to the topic.
Steps to Reproduce
1.set enableControllerMode=true
2.start broker
3.then the broker will keep printing log "Init the confirmOffset" in store.log
What Did You Expect to See?
log "Init the confirmOffset" should't print so frequently
What Did You See Instead?
the broker keeps printing log "Init the confirmOffset"
Additional Context
No response
The text was updated successfully, but these errors were encountered: