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
Centos
RocketMQ version
5.2.1
JDK Version
11
Describe the Bug
When asynchronously sending messages, if num is obtained but size is not obtained under the back pressure control, num cannot be released and the sending rate is affected.
Steps to Reproduce
null
What Did You Expect to See?
When asynchronously sending messages, if num is obtained but size is not obtained under the back pressure control,num can be released, which affects the sending rate.
What Did You See Instead?
null
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
Centos
RocketMQ version
5.2.1
JDK Version
11
Describe the Bug
When asynchronously sending messages, if num is obtained but size is not obtained under the back pressure control, num cannot be released and the sending rate is affected.
Steps to Reproduce
null
What Did You Expect to See?
When asynchronously sending messages, if num is obtained but size is not obtained under the back pressure control,num can be released, which affects the sending rate.
What Did You See Instead?
null
Additional Context
No response
The text was updated successfully, but these errors were encountered: