-
Notifications
You must be signed in to change notification settings - Fork 748
[GOBBLIN-1956]Make Kafka streaming pipeline be able to config the max poll records during runtime #3827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
[GOBBLIN-1956]Make Kafka streaming pipeline be able to config the max poll records during runtime #3827
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d17a6c4
address comments
be0f096
use connectionmanager when httpclient is not cloesable
922b014
add uite test
b6ac16f
fix typo
76696ca
[GOBBLIN-1956] Make Kafka streaming pipeline be able to config the ma…
807027f
small refractor
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the intuition behind a 50 MB default max buffer size?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it have to do with
in gobblin-kafka-jobs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no relationship between those two config. The value should not be super small as we need to guarantee the performance, and not super large as we want to avoid OOM issue. So I gave 50MB here as default. And this should only take effect when record size are large, for normal topic, it should fall back to use KAFKA_MAX_POLL_RECORDS_KEY
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. I think 50MB seems like a good default.
Here's an example of how the throughput would look for some higher volume topics. All topics under 5kb would be able to do 1000 records per second (pageviewevent is only ~800bytes and URE is ~3MB).