[SERVER-48806] Obtain and persist donor optimes in MigrationServerInstance Created: 15/Jun/20 Updated: 29/Oct/23 Resolved: 29/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-B | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2020-09-07, Repl 2020-09-21, Repl 2020-10-05 | ||||||||
| Participants: | |||||||||
| Description |
|
This should obtain the startApplyingOpTime (top of donor oplog) and startFetchingOpTime (oldest open transaction optime related to tenant on donor) and persist them to the config.migrations.<migrationId> table. |
| Comments |
| Comment by Githook User [ 23/Sep/20 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |