[SERVER-50582] Create delineation between cloning initial data and cloning oplog entries on the donor state machine Created: 27/Aug/20 Updated: 29/Oct/23 Resolved: 02/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Vishnu Kaushik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2, PM-234-T-lifecycle, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-11-02 |
| Participants: |
| Description |
|
Turn kDonating into kDonatingInitialData and kDonatingOplogEntries. The coordinator will tell the donor to transition into both states. A necessary precursor for the donor transitioning into kDonatingOplogEntries is all recipients telling the coordinator that they are finished cloning and are now applying. This change allows us to unpin durable history after the recipients have stopped reading initial data from after that timestamp. |
| Comments |
| Comment by Githook User [ 26/Oct/20 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |