[SERVER-49204] Implement donorForgetMigration command Created: 30/Jun/20  Updated: 29/Oct/23  Resolved: 09/Sep/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-A
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-50191 Create TTL index on config.tenantMigr... Closed
is depended on by SERVER-50528 Test a tenant migration end to end wi... Closed
Related
related to SERVER-50807 [passthrough suite] Make ContinuousTe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-08-24, Sharding 2020-09-21
Participants:

 Description   

donorForgetMigration just needs to ensure the migration-related state on the donor and recipient get cleaned up (Cloud will delete the data from the donor or recipient as needed).

Once the donor's logic is in a future chain, TenantMigrationDonor can have a "_receivedDonorForgetMigration" promise that it waits on once it finishes coordinating the migration.

The donorForgetMigration command can set this promise by, e.g., looking up the TenantMigrationDonor if one exists and calling TenantMigrationDonor::receivedDonorForgetMigration, which emplaces the promise.

The donor can then proceed with the rest of the chain, which should just be one step to update its state machine doc to mark it as garbage collectable by the TTL index.



 Comments   
Comment by Githook User [ 09/Sep/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-49204 Implement donorForgetMigration command
Branch: master
https://github.com/mongodb/mongo/commit/3626a65b1d1f8ff2d230704146a09595f78bfe51

Comment by Esha Maharishi (Inactive) [ 08/Aug/20 ]

CC cheahuychou.mao, moving this out of next sprint since it's easier to test this ticket after SERVER-50191 is in, which may be implemented as part of PM-1810.

If needed, this ticket can be pulled back in and implemented before SERVER-50191 by, e.g., making the test directly create a TTL index on config.migrationDonors.

Generated at Thu Feb 08 05:19:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.