gaozhangmin opened a new pull request, #20052:
URL: https://github.com/apache/pulsar/pull/20052

   ### Motivation
   
   Currently, Pulsar's Dynamic Configuration Feature only supports 
cluster-level configuration, meaning that any changes made to the dynamic 
configuration apply to all brokers in the cluster. 
   
   This pull request proposes a new feature that allows for broker-level 
configuration, meaning that changes made to the dynamic configuration will only 
affect specific machines in the cluster, rather than all of them.
   
   
   ### Modifications
   Add new parameters `scope` to admin commands `update-dynamic-config`, 
`delete-dynamic-config`, `get-all-dynamic-config` , scope value is cluster or 
broker's LookupServiceAddres.
   
   ### Verifying this change
   
   1. org.apache.pulsar.admin.cli.PulsarAdminToolTest#brokers
   2. 
org.apache.pulsar.broker.admin.AdminApiTest#testUpdateDynamicLoadBalancerSheddingIntervalMinutes
   
   ### Does this pull request potentially affect one of the following parts:
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   *If the box was checked, please highlight the changes*
   
   - [ ] Dependencies (add or upgrade a dependency)
   - [ ] The public API
   - [ ] The schema
   - [ ] The default values of configurations
   - [ ] The threading model
   - [ ] The binary protocol
   - [ ] The REST endpoints
   - [ ] The admin CLI options
   - [ ] The metrics
   - [ ] Anything that affects deployment
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   
   ### Matching PR in forked repository
   
   PR in forked repository:  https://github.com/gaozhangmin/pulsar/pull/12
   


-- 
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]

Reply via email to