We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
any
develop
No response
whern isPopShouldStop hit, we should release the lock
review the code
The text was updated successfully, but these errors were encountered:
[ISSUE #8601]When isPopShouldStop hit,unlock queueLockManager (#8602)
1a15729
* fix:when isPopShouldStop hit, unlock queueLockManager * fix:when isPopShouldStop hit, unlock queueLockManager * fix: limit rate of appending commit in case of DLedger commit-log Signed-off-by: Zhanhui Li <lizhanhui@gmail.com> --------- Signed-off-by: Zhanhui Li <lizhanhui@gmail.com> Co-authored-by: Zhanhui Li <lizhanhui@gmail.com>
Successfully merging a pull request may close this issue.
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
any
RocketMQ version
develop
JDK Version
No response
Describe the Bug
whern isPopShouldStop hit, we should release the lock
Steps to Reproduce
review the code
What Did You Expect to See?
review the code
What Did You See Instead?
review the code
Additional Context
No response
The text was updated successfully, but these errors were encountered: