txHandler: do not drop accepted mgs #6257
Open
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.
Summary
The
(!isCMEnabled && congestedERL)
condition in incomingMsgErlCheck added at some point to relief the spam congestion has the following side effect when:isCMEnabled
) not enabled yet (it will be after the currentConsumeCapacity
invocation)In this case the condition
(!isCMEnabled && congestedERL)
triggers congestion control to be enabled and dropping this message. In the same time consecutive messages would come through becauseisCMEnabled
is set anderl.cm.ShouldDrop(c)
might allow it due to messages rate.Fixed by enabling congestion control but accepting the message if
(!isCMEnabled && congestedERL)
is met.Note to reviewers:
This fix came out from ERL work and is is also integrated into the ERL change #6176
Test Plan
Rely on existing tests