[SERVER-21478] Fix lag between updating optime after minvalid leaving node in recovering Created: 16/Nov/15  Updated: 17/Nov/15  Resolved: 16/Nov/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.2.0-rc3

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-21484 Race writing minvalid doc when becomi... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

Due to how we now wait for journaling before updating our optime the check in tryToGoLiveAsSecondary will not work until apply batches (setting new optimes) stop, or sync with our optime.



 Comments   
Comment by Githook User [ 16/Nov/15 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-21478: use lastWrite instead of replCoord::lastOpTime when transitioning to secondary
Branch: master
https://github.com/mongodb/mongo/commit/bd58ea2ba5d17b960981990bb97cab133d7e90ed

Generated at Thu Feb 08 03:57:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.