[SERVER-41391] Clear the oplogTruncateAfterPoint timestamp on stepdown Created: 30/May/19 Updated: 29/Oct/23 Resolved: 05/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2019-06-17, Execution Team 2019-07-01, Execution Team 2019-07-29, Execution Team 2019-08-12, Execution Team 2019-11-04, Execution Team 2019-11-18 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We will be setting the oplogTruncateAfterPoint continuously in mode PRIMARY so that we can safely replicate before journaling. UPDATE: we are pivoting to unsetting the value on stepdown, as opposed to removing the invariant on stepup. |
| Comments |
| Comment by Githook User [ 05/Nov/19 ] |
|
Author: {'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}Message: |