[SERVER-26415] Make sure to catch up to minValid before exiting rollback Created: 30/Sep/16  Updated: 20/Sep/17  Resolved: 03/Nov/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Judah Schvimer
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-26570 MongoDB Slave Crashed During Replication Closed
is related to SERVER-23070 rewrite SyncSourceResolver to select ... Closed
is related to SERVER-25145 During rollback (or w/minvalid invali... Closed
Operating System: ALL
Sprint: Repl 2016-11-21
Participants:
Case:
Linked BF Score: 0

 Description   

Not doing so can (among other problems) result in an "Unrecoverable rollback error" if the node ever rolls back a second time.



 Comments   
Comment by Spencer Brody (Inactive) [ 03/Nov/16 ]

We wound up fixing the underlying issue in a slightly different way in SERVER-25145, by allowing ourselves to leave ROLLBACK state and transition to RECOVERING, but ensuring that we'll only pick sync sources that contain minValid.

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