-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
KAFKA-15776: Support added to update remote.fetch.max.wait.ms dynamically #16203
Conversation
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.
Thanks for the PR. Left some minor comments.
core/src/test/scala/unit/kafka/server/DynamicBrokerConfigTest.scala
Outdated
Show resolved
Hide resolved
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.
LGTM!
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.
Thanks @kamalcph for the PR, overall LGTM. Left a minor comment in the test.
assertThrows(classOf[ConfigException], () => config.dynamicConfig.validate(newProps, perBrokerConfig = false)) | ||
// invalid value "0" | ||
newProps.put(RemoteLogManagerConfig.REMOTE_FETCH_MAX_WAIT_MS_PROP, "0") | ||
assertThrows(classOf[ConfigException], () => config.dynamicConfig.validate(newProps, perBrokerConfig = true)) |
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.
Can you also check perBrokerConfig = false
for value 0 like you did for negative value -1 in the earlier code?
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.
Thanks @kamalcph for addressing the review comments. LGTM.
A few test failures that are unrelated to this change, will merge it to trunk and 3.8 branches. |
@kamalcph Can you raise a PR against 3.8 branch as I would like those changes to be reviewed in PR as it has conflicts with that branch? |
…ally (apache#16203) Reviewers: Satish Duggana <[email protected]>, Luke Chen <[email protected]>
Opened #16275 and #16276 to cherry-pick the KAFKA-15776 feature to the 3.8 branch. PTAL. |
…ally (#16203) Reviewers: Satish Duggana <[email protected]>, Luke Chen <[email protected]>
…ally (apache#16203) Reviewers: Satish Duggana <[email protected]>, Luke Chen <[email protected]>
Committer Checklist (excluded from commit message)