[SERVER-15981] Re-enable rollback_too_new.js with logic that doesn't violate WT oplog assumptions Created: 06/Nov/14  Updated: 11/Jul/16  Resolved: 13/Nov/14

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 2.8.0-rc1

Type: Bug Priority: Critical - P2
Reporter: Ian Whalen (Inactive) Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 13/Nov/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-15981 rework rollback_too_new.js to be WiredTiger compatible
Branch: master
https://github.com/mongodb/mongo/commit/a38dbb08df9b4bafc94a54da07746950048a4e41

Comment by Githook User [ 06/Nov/14 ]

Author:

{u'username': u'IanWhalen', u'name': u'Ian Whalen', u'email': u'ian.whalen@gmail.com'}

Message: SERVER-15981 Disable rollback_too_new.js
Branch: master
https://github.com/mongodb/mongo/commit/386a8f28bb8cc830b8ff9a311f56fab06677e209

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