RexXiong opened a new pull request, #2100:
URL: https://github.com/apache/incubator-celeborn/pull/2100
<!--
Thanks for sending a pull request! Here are some tips for you:
- Make sure the PR title start w/ a JIRA ticket, e.g. '[CELEBORN-XXXX]
Your PR title ...'.
- Be sure to keep the PR description updated to reflect all changes.
- Please write your PR title to summarize what this PR proposes.
- If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
This PR introduce dynamic ConfigService at SystemLevel and TenantLevel,
Dynamic configuration is a type of configuration that can be changed at runtime
as needed. It can be used at system level/tenant level. When applying dynamic
configuration, the priority order is as follows: tenant level overrides system
level, which in turn overrides static configuration(CelebornConf). This means
that if a configuration is defined at the tenant level, it will be used instead
of the system level or static configuration(CelebornConf). If the tenant-level
configuration is missing,
the system-level configuration will be used. If the system-level
configuration is also missing, CelebornConf
will be used as the default value.
There are several other tasks related to this feature that will be
implemented in the future.
- [ ] [Add isDynamic property for
CelebornConf](https://issues.apache.org/jira/browse/CELEBORN-1051)
- [ ] [Support DB based
Configserver](https://issues.apache.org/jira/browse/CELEBORN-1054)
- [ ] [Add restAPI for configuration
management](https://issues.apache.org/jira/browse/CELEBORN-1056)
### Why are the changes needed?
The current configuration of the server (CelebornConf) is static. When the
configuration is changed, the service needs to be restarted. This PR introduces
a dynamic configuration solution. The server side can use dynamic configuration
as needed. At the same time, it is considered that the tenant level will be
supported in the future (such as supporting tenant level dynamic quota control)
configuration, so this time we will also consider supporting dynamic
tenant-level configuration, and this PR will provide a default implementation
based on the file system.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
UT
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
