feat: add boolean flag 'share_leader_conn' in consumer config #598
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
zmstone
force-pushed
the
0921-consumer-exclusive-own-connection
branch
2 times, most recently
from
ffc8faa
to
f9dbe94
Compare
Introduced `share_leader_conn` consumer config option. Set to `true' to consume less TCP connections towards Kafka, but may lead to higher fetch latency. This is because Kafka can ony accumulate messages for the oldest fetch request, later requests behind it may get blocked until `max_wait_time' expires for the oldest one
zmstone
force-pushed
the
0921-consumer-exclusive-own-connection
branch
from
f9dbe94
to
6ee6c85
Compare
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.
fixes #577
Introdced
share_leader_connconsumer config option (default =false).Set to
trueto consume less TCP connections towards Kafka, but may lead to higher fetch latency.This is because Kafka can ony accumulate messages for the oldest fetch request for each connection,
later requests behind it may get blocked until
max_wait_timeexpires for the oldest one