Skip to content
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

Make Default byte in rate and Msg in rate configurable #864

Merged
merged 8 commits into from
Nov 8, 2021

Conversation

vmaheshw
Copy link
Collaborator

@vmaheshw vmaheshw commented Nov 5, 2021

The default values set may need to be changed based on the specific scenario. Specifically, this brings a dependency that if the default throughput rate per task in 5MB and the default is 5KB, it implies that a task can only process 1000 partitions. Making this a configurable property will make it customizable based on the requirement.

Note: This change does not cover config at a datastream level. We can add it based on the requirement.

shrinandthakkar
shrinandthakkar previously approved these changes Nov 5, 2021
Vaibhav Maheshwari added 2 commits November 5, 2021 17:27
Copy link
Collaborator

@jzakaryan jzakaryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@vmaheshw vmaheshw merged commit 98880fc into linkedin:master Nov 8, 2021
vmaheshw added a commit to vmaheshw/brooklin that referenced this pull request Mar 1, 2022
The default values set may need to be changed based on the specific scenario. Specifically, this brings a dependency that if the default throughput rate per task in 5MB and the default is 5KB, it implies that a task can only process 1000 partitions. Making this a configurable property will make it customizable based on the requirement.

Note: This change does not cover config at a datastream level. We can add it based on the requirement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants