-
Notifications
You must be signed in to change notification settings - Fork 141
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
[FEATURE] Support the hot reload of coordinator's configuration rss.coordinator.shuffle.nodes.max
#410
Comments
Maybe we can extend this issue title to a bit more generic: Once uniffle supports deployments on K8S, it's common to hot-reload configurations backend by using |
@jerqi Do you have time for this issue. I'd like this feature to be merged in our next release, such as 0.6.1 or 0.7.0 |
I will finish this issue this week. |
) ### What changes were proposed in this pull request? I refer to Hadoop implement. I design a hot reload process. We support nodeMax at first. ### Why are the changes needed? It's more convenient. ### Does this PR introduce _any_ user-facing change? add `rss.reconfigure.interval.sec`. ### How was this patch tested? UT Co-authored-by: roryqi <roryqi@tencent.com> Co-authored-by: Kaijie Chen <ckj@apache.org>
Code of Conduct
Search before asking
Describe the feature
rss.coordinator.shuffle.nodes.max
don't support hot reload. It's not friendly for operation.Motivation
It will be more friendly for operation
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: