-
Notifications
You must be signed in to change notification settings - Fork 14k
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-17031: Make RLM thread pool configurations public #17499
Conversation
According to KIP-950, remote.log.manager.thread.pool.size should be marked as deprecated and replaced by two new configurations: remote.log.manager.copier.thread.pool.size and remote.log.manager.expiration.thread.pool.size. Signed-off-by: Federico Valeri <[email protected]>
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.
Looks good, a question about the default value though
storage/src/main/java/org/apache/kafka/server/log/remote/storage/RemoteLogManagerConfig.java
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!
Signed-off-by: Federico Valeri <[email protected]>
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 @fvaleri for the PR, left a comment.
storage/src/main/java/org/apache/kafka/server/log/remote/storage/RemoteLogManagerConfig.java
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! Thanks for tohe fix.
This is a bit confusing IMO. What if the user sets -2? I think that we can use -1 as default, and fallback when value is <=0. Wdyt? I also have a test to fix. |
Signed-off-by: Federico Valeri <[email protected]>
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
-2 is invalid value and it will fail. The valid values are -1 and value >0. -1 indicates to be |
@satishd thanks for the feedback. Latest commit should address your request. |
Signed-off-by: Federico Valeri <[email protected]>
2301f67
to
106ac74
Compare
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 @fvaleri for the updates. Can you please add validation for these configs(remote.log.manager.copier.thread.pool.size, remote.log.manager.expiration.thread.pool.size) and the respective UTs?
Signed-off-by: Federico Valeri <[email protected]>
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 @fvaleri for updating the PR. Please address the below items.
- It seems there are testfailures because of style checks.
- Add a UT to verify that the copier and expiration threadpools fallsback to the expected default value(10) if not configured.
Signed-off-by: Federico Valeri <[email protected]>
Test failures are unrelated. They work locally and are reported as flaky. |
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
Since this changes the behavior of the new tiered storage configurations, we will need to get it into 3.9 if it is to get in at all. I will commit it now. |
…lt handling (#17499) According to KIP-950, remote.log.manager.thread.pool.size should be marked as deprecated and replaced by two new configurations: remote.log.manager.copier.thread.pool.size and remote.log.manager.expiration.thread.pool.size. Fix default handling so that -1 works as expected. Reviewers: Luke Chen <[email protected]>, Gaurav Narula <[email protected]>, Satish Duggana <[email protected]>, Colin P. McCabe <[email protected]>
…lt handling (apache#17499) According to KIP-950, remote.log.manager.thread.pool.size should be marked as deprecated and replaced by two new configurations: remote.log.manager.copier.thread.pool.size and remote.log.manager.expiration.thread.pool.size. Fix default handling so that -1 works as expected. Reviewers: Luke Chen <[email protected]>, Gaurav Narula <[email protected]>, Satish Duggana <[email protected]>, Colin P. McCabe <[email protected]>
According to KIP-950,
remote.log.manager.thread.pool.size
should be marked as deprecated and replaced by two new configurations:remote.log.manager.copier.thread.pool.size
andremote.log.manager.expiration.thread.pool.size
.