Demonstrate the capacity limiter lockup effect with a demo #3033
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When executing we see the following output in the console: ``` ... !!!!!!!!!.!..!!!!!!!!!!!!!!!!.!!!!.!!.!.!!!.!!.!..!..!...!....!..!.!!!!!!!!!...!..!!!.!.!!!!..!!!.!. !!!!!!!!!!!!!!...!!!!.!.!........!...!!!!.!!!!!.......!.!.!.!!.!!....!...!...!!!..!.!.!!!!!!!!!..!.! !.!!!!...!....!...!.!!.!!....!.!!!!!!!!!!!!.!..!!!!!!!!!!!!!!.!!.!...!....!......!!!!!!!!!!!....!!!! !!!!!!!!!!!.!...!!!!.!.!!!!..!..!.!.!.!!!!!!!!!!!!..!!!!!!!!!!!!!...!!!!!!!!!!!!!!!!!!!!!!!!.......!! !.....!..!!!!!!!!!!!...!.!.!..!.!.!!!!.!!!!!!.!!!....!....!.!..!!!!!!!!!!.!!!!!!!!!!!!!!!.!.!!!!!!!!! !!!!!!......!....!.!!!!!!!!!!...!!!!!..!.!.!..!..!...!!!.!!!!!!!!!!.......!......!....!....!!!!!!! !!!!!!.!!.!!!!!!!!!!!!!!!.....!!..!.!.!....!......!!.!.!!!..!!!!!!!!!!!!..!.!.!!.!!...!!.!!!!!!!!!!! ..!!!!!!!!!!!!!!!...!!!!!!!!!!!..!!!!.!!!!!...!!!!!!!!!!!!.!!.!!!!!!!!!!!!!!....!.!....!!!!!!!!!!!!! !!!!..!..!.....!.!!!!!!!!.!.!!...!!!!!..!......!....!!!!.!!!!!!!!!!!!!!!!!!!!!....!.!........!!!.!.. ..!..!!!!!!!!!!!!!!!!2024-08-06 10:32:03,251 servicetalk-global-io-executor-1-2 [WARN ] HttpMessageDiscardWatchdogClientFilter - Discovered un-drained HTTP response message body which has been dropped by user code - this is a strong indication of a bug in a user-defined filter. Response payload (message) body must be fully consumed before discarding. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!! Consecutive failure threshold reached (200). Terminating. Terminating. ``` There is a very strong correlation with lockup and the watchdog filter emitting a message (we don't lockup every time we see a message, but everytime we lockup we see a message right before).
bryce-anderson
force-pushed
the
bl_anderson/lockup-repro
branch
from
48e1bd6
to
535ed2b
Compare
This was referenced Aug 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When executing we see the following output in the console:
There is a very strong correlation with lockup and the watchdog filter emitting a message (we don't lockup every time we see a message, but everytime we lockup we see a message right before).