[SERVER-26071] log latest op in catchup.js on error Created: 12/Sep/16  Updated: 07/Feb/17  Resolved: 12/Sep/16

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

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Sprint: Repl 2016-09-19
Participants:
Linked BF Score: 0

 Description   

We currently check if the latest op is in the oplog, but when we don't see the op we don't log what op was missing. Logging that op would ease debugging the test.



 Comments   
Comment by Githook User [ 12/Sep/16 ]

Author:

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

Message: SERVER-26071 log latest op in catchup.js on error
Branch: master
https://github.com/mongodb/mongo/commit/15782d3342a6e329288905e3157556654457321e

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