BewareMyPower opened a new pull request #8133: URL: https://github.com/apache/pulsar/pull/8133
### Motivation When multiple broker clusters shared the same bookie cluster, if user wanted to remove a broker cluster, the associated ledgers in bookies should also be deleted. ### Modifications - Add an option to `cluster delete` command to delete all the data associated with the cluster. Currently there's no way to delete the ledgers of schema from client's side, a new REST API to delete schema's ledgers should be exposed or the existed `SchemaRegistryServiceImpl#deleteSchema`'s semantics should be change. ### Verifying this change - [ ] Make sure that the change passes the CI checks. The new option has been tested in local environment by: 1. Deploy a ZK which acts as both local ZK and the configuration store; 2. Init metadata of 2 clusters, the 2nd cluster use `--bookkeeper-metadata-service` option to share the same BK metadata position; 3. Deploy a BK; 4. Deploy 2 brokers associated with the 2 clusters' metadata; 5. Create some topics and produce some messages to 2 clusters; 6. Run `bin/pulsar cluster -all <cluster>` to delete the whole cluster, use `bin/bookkeeper shell list ledgers` to verify the change of ledgers count. **An integration test is needed to simulate the procedures above.** ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
