[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: SERVER-34978 Upgrade could trigger invariant in replication recovery
Branch: master
https://github.com/mongodb/mongo/commit/41b83a16fd3d308a24f2e001759d8415dc348ddf

Generated at Thu Feb 08 04:38:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.