[
https://issues.apache.org/jira/browse/INLONG-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated INLONG-389:
----------------------------------
Labels: pull-request-available (was: )
> Add broker-range configuration options for configuration changes
> ----------------------------------------------------------------
>
> Key: INLONG-389
> URL: https://issues.apache.org/jira/browse/INLONG-389
> Project: Apache InLong
> Issue Type: Improvement
> Reporter: Guocheng Zhang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When adding, modifying, or deleting the default Broker configuration or Topic
> configuration, we need the caller to specify the specific broker‘s scope of
> operations and which brokers to operate on. In actual use, if the business
> needs to deploy the topic on the entire cluster, or just want to specify how
> many brokers to deploy, this setting is awkward.
> Some businesses propose that it is best to provide a configuration parameter
> of the scope of influence of the broker during operation, and the Master
> handle which broker nodes are deployed to.
> It is planned to increase the broker-range configuration options for
> configuration changes: when carrying this configuration, the Master
> selectively deploys topic according to the specified number of broker nodes
> and the number of topic deployments on each Broker; if the request carries
> the configuration option of brokerId, then the broker-range configuration is
> ignore and the configuration change is operated based on the brokerId
> configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
