[SERVER-40976] rollback_after_enabling_majority_reads.js should not run on mmapv1 Created: 03/May/19  Updated: 29/Oct/23  Resolved: 03/May/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.9
Fix Version/s: 4.0.10

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-05-20
Participants:
Linked BF Score: 50

 Description   

This test assumes that recover-to-timestamp is used when enableMajorityReadConcern=true, but mmapv1 always uses rollback-via-refetch.



 Comments   
Comment by Githook User [ 03/May/19 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-40976 rollback_after_enabling_majority_reads.js should not run on mmapv1
Branch: v4.0
https://github.com/mongodb/mongo/commit/c8db06caa4f803b9966bbc889564718a105b3c7e

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