Fix the flush callback might be called repeatedly #353
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #352
Motivation
#303 adds the flush callback to the last
OpSendMsg
instead of adding to the batch message container. However,batchMessageAndSend
will create anOpSendMsg
and add it to thependingMessagesQueue_
.pulsar-client-cpp/lib/ProducerImpl.cc
Lines 384 to 389 in 7bb94f4
In the code above,
pendingMessagesQueue_
could never be empty and the callback will be added again byopSendMsg->addTrackerCallback
. The 1st time it's added increateOpSendMsg
orcreateOpSendMsgs
called bybatchMessageAndSend
.Motivation
Add the callback to the last `OpSendMsg only when the batch message container is empty.
In
testFlushBatch
, replace theflush
call with theflushAsync
call and verify the callback is only called once after it's completed.Documentation
doc-required
(Your PR needs to update docs and you will update later)
doc-not-needed
(Please explain why)
doc
(Your PR contains doc changes)
doc-complete
(Docs have been already added)