[SERVER-25975] Print oplog on failures in optime.js Created: 06/Sep/16  Updated: 19/Nov/16  Resolved: 07/Sep/16

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

Type: Bug 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
is related to SERVER-26869 Add a predicate to dumpOplog call in ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2016-09-19
Participants:
Linked BF Score: 0

 Description   

optime.js occasionally fails with an oplog mismatch error. We currently don't print out the oplog on these mismatches, just the mismatched optime. Printing out the oplog would make it clear what was going wrong.



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

Author:

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

Message: SERVER-25975 print oplog on failures in optime.js
Branch: master
https://github.com/mongodb/mongo/commit/2576c69fbb31b7b4c67ac8835fc2a5f6d405ce8a

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