[revert][misc] "modify check waitingForPingResponse with volatile (#12615)" #19439
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.
This reverts commit 62e2547.
Motivation
The motivation for #12615 relies on an incorrect understanding of Netty's threading model. The
ctx.executor()is the context's event loop thread that is the same thread used to process messages. ThewaitingForPingResponsevariable is only ever updated/read from the context's event loop, so there is no need to make the variablevolatile.Modifications
volatilekeyword forwaitingForPingResponseVerifying this change
Read through all references to the variable.
Documentation
doc-not-neededMatching PR in forked repository
PR in forked repository: Skipping for this trivial PR.