[fix][client]Fix MaxQueueSize semaphore release leak in createOpSendMsg - #16915
Conversation
|
There is a conflict when direct merge this to branch 2.7 |
|
Please also help to cherry-pick to branch 2.9 |
@mattisonchao ok, I'll cherry-pick it to branch 2.9. |
|
|
Move |
|
@Nicklee007 Please provide a correct documentation label for your PR. |
@mattisonchao branch 2.9 cherry-pick PR #16958, PTAL. |
|
@Nicklee007 Please provide a correct documentation label for your PR. |
Co-authored-by: nicklixinyang <nicklixinyang@didiglobal.com>
|
Move |
|
@Nicklee007 Please provide a correct documentation label for your PR. |
…sg (apache#16915) (cherry picked from commit d95f6cf) (cherry picked from commit 70f1a03)
Motivation
Release MaxQueueSize semaphore when invalid message, the related PR #16835 only release the memory usage, but the semaphore also need release in here.
The fixed unit test can reproduce it, which only
enableBatchingcan invoke thecreateOpSendMsginBatchMessageContainerImpl.Modifications
Documentation
doc-not-needed(Please explain why)