[SERVER-34978] Upgrade could trigger invariant in replication recovery Created: 14/May/18 Updated: 29/Oct/23 Resolved: 14/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2018-05-21 |
| Participants: |
| Description |
|
We allow upgrades after unclean shutdown. After an unclean shutdown, it's possible we'd have a non-null appliedThrough and a null stableTimestamp in wiredTiger (so it wouldn't be boost::none). We should add an "|| stableTimestamp->isNull()" check to this invariant: https://github.com/mongodb/mongo/blob/d12afa4fdda9c6b113e7be3b4d67d757b07b50b5/src/mongo/db/repl/replication_recovery.cpp#L215-L219 |
| Comments |
| Comment by Githook User [ 14/May/18 ] |
|
Author: {'name': 'Judah Schvimer', 'email': 'judah@mongodb.com', 'username': 'judahschvimer'}Message: |