[SERVER-25034] Remove ErrorCodes::OplogOutOfOrder block from DataReplicator::_onOplogFetchFinish Created: 13/Jul/16  Updated: 13/Aug/16  Resolved: 01/Aug/16

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

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Repl 18 (08/05/16)
Participants:
Linked BF Score: 0

 Description   

This was needed when we didn't maintain the hash in _lastFetched.



 Comments   
Comment by Githook User [ 02/Aug/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-25034 reset initial sync state after resetting reporter and applier
Branch: master
https://github.com/mongodb/mongo/commit/9e81511add86eacc24ba14d43622a1a71a9594c2

Comment by Githook User [ 01/Aug/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-25034 remove OplogOutOfOrder block from DataReplicator::_onOplogFetchFinish
Branch: master
https://github.com/mongodb/mongo/commit/2ed489b884676ae93bcf6373b49a2a838979b693

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