[SERVER-50034] Make donor send recipientSyncData to the recipient with its blockTimestamp Created: 30/Jul/20 Updated: 29/Oct/23 Resolved: 04/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-A | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-08-10 |
| Participants: |
| Description |
|
After the donor has started blocking writes, the donor should send recipientSyncData with returnAfterReachingOpTime: <blockOpTime> to the recipient.
Since the 'updateDonorStateDocument' function mutates the donorStateDoc object in 'startMigration', we can directly pass down the donorStateDoc object into the sendRecipientSyncDataCommand. |
| Comments |
| Comment by Githook User [ 04/Aug/20 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |