[fix][flaky-test]ProxyConnectionThrottlingTest.testInboundConnection #17883
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:
Motivation
this test is executed as follows:
But the execution logic of
step-3
is like this:DefaultConnectionController.totalConnectionNum
State.REACH_MAX_CONNECTION_PER_IP
founded, do close connection which will decrementDefaultConnectionController.totalConnectionNum
Then the problem is that the connection closes was executed asynchronously(see code below), if the main thread executes fast enough, the assert
Assert.assertEquals(ConnectionController.DefaultConnectionController.getTotalConnectionNum(), 4)
will fail, because the last connection has not close finish.pulsar/pulsar-proxy/src/main/java/org/apache/pulsar/proxy/server/ProxyConnection.java
Lines 153 to 165 in bde5ac7
Modifications
Change the assertion logic to executed using
Awaitility
Documentation
doc-not-needed
Matching PR in forked repository
PR in forked repository: