[improve] [broker] Do not call cursor.isCursorDataFullyPersistable if disabled dispatcherPauseOnAckStatePersistentEnabled #22729
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.
Motivation
The method
cursor.isCursorDataFullyPersistable
was added with PIP-299-part-1: Stop dispatch messages if the individual acks will be lost in the persistent storage, it used to check if the dispatching should be pause.Calling
cursor.isCursorDataFullyPersistable
will loop the collectioncursor.individualDeletedMessages
. It isnot a light method. If never enabled "dispatcherPauseOnAckStatePersistentEnabled", should avoid calling
cursor.isCursorDataFullyPersistable
.Modifications
Avoid calling
cursor.isCursorDataFullyPersistable
if disableddispatcherPauseOnAckStatePersistentEnabled
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: x