[SERVER-56096] Invariant failure in ReplicationRecoveryImpl::recoverFromOplog Created: 14/Apr/21  Updated: 29/Oct/23  Resolved: 28/Oct/21

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.23
Fix Version/s: 4.2.18, 4.0.28

Type: Bug Priority: Major - P3
Reporter: Dmitry Agranat Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: Atlas_Failure_Analysis
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-48707 Disable replication recovery invarian... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2021-05-31, Repl 2021-06-14, Repl 2021-06-28, Repl 2021-07-12, Repl 2021-07-26, Repl 2021-08-09, Repl 2021-10-18, Repl 2021-11-01
Participants:
Case:

 Description   

2021-03-29T21:16:25.289+0000 F -        [rsBackgroundSync] Invariant failure !stableTimestamp || stableTimestamp->isNull() || appliedThrough.isNull() || *stableTimestamp == appliedThrough.getTimestamp() Stable timestamp Timestamp(1617051638, 32) does not equal appliedThrough timestamp { ts: Timestamp(1617051019, 1), t: 287 } src/mongo/db/repl/replication_recovery.cpp 262
2021-03-29T21:16:25.289+0000 F -        [rsBackgroundSync] \n\n***aborting after invariant() failure\n\n



 Comments   
Comment by Githook User [ 28/Oct/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-56096 Remove replication recovery invariant that stableTimestamp equals appliedThrough
Branch: v4.0
https://github.com/mongodb/mongo/commit/8fbb41841fd30a18a66f8d12e5c87cec7649bc86

Comment by Githook User [ 28/Oct/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-56096 Remove replication recovery invariant that stableTimestamp equals appliedThrough
Branch: v4.2
https://github.com/mongodb/mongo/commit/4c689d6ec00a0664ce56b87e305eb1af0d7a3f7f

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