[SERVER-45668] Stop writing the oplogTruncateAfterPoint as a 1-node-replica-set primary Created: 21/Jan/20 Updated: 27/Jan/20 Resolved: 27/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Follow work for |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 27/Jan/20 ] |
|
Closing this task. I originally thought it was possible, but it is not presently, in any nice way. replSetReconfig can make a single node replica set primary into a sync source at any time, before even sending replSetReconfig to that node to tell it that it is now part of a larger replica set. There is also no good way to atomically set the reconfig state and write the first oplogTruncateAfterPoint value. |