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

   
   ### Motivation
   
   Right now after we mark the topic migrated, replicators do not get 
disconnected from blue cluster and subscriptions are not deleted even after the 
backlog is drained and all consumers are disconnected. This pr takes care of 
this by asynchronously disconnecting replicators and deleting subscriptions 
once the backlog is drained and all consumers are disconnected when 
checkClusterMigration API is called.
   
   ### Modifications
   
   Replicators without backlog are disconnected and subscriptions without 
consumers are deleted and eventually topic is garbage collected in the blue 
cluster.
   
   ### Verifying this change
   
   This change added tests and can be verified as follows:
   
   Added unit tests to verify the change
   
   ### 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 -->
   


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