[client] Change the default value of 'netty.client.num-network-threads' to 3 to avoid netty channel congestion #1642
Conversation
This file contains hidden or 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
…s' to 3 to avoid netty channel congestion
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.
Purpose
Linked issue: close #1641
LogScanner's consumption latency keeps increasing during cluster upgrades. It appears the upgrade caused a Netty worker to hang. Fluss currently defaults to only 1 Netty worker thread (netty.client.num-network-threads=1), resulting in network channel congestion. The issue disappears when increasing netty.client.num-network-threads to 3.
Brief change log
Tests
API and Format
Documentation