[Java Client] Improve consumer listener logic #13273
Merged
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
In #13023, we updated the Java client's consumer listener logic to ensure correct ordering of messages received. We can simplify the logic for the variable named
executorQueueSize
. It can bevolatile
instead ofatomic
and it can be a boolean instead of an integer.Modifications
executorQueueSize
toisListenerHandlingMessage
inConsumerBase
and make itvolatile
instead ofAtomic
internalPinnedExecutor
inConsumerImpl
Verifying this change
This is a trivial change.
Does this pull request potentially affect one of the following parts:
This is not a breaking change.
Documentation
no-need-doc
This is an internal change.