[SERVER-34804] Secondary reads tests should only run on snapshot-enabled storage engines Created: 02/May/18  Updated: 29/Oct/23  Resolved: 10/May/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.7.9
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
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: Storage NYC 2018-05-21
Participants:
Linked BF Score: 91

 Description   

The secondary reads tests secondary_reads_timestamp_visibility.js should not run on storage engines that do not support snapshot reads. The test depends on reading during batches that introduces hangs in MMAP and ephemeralForTest.



 Comments   
Comment by Githook User [ 10/May/18 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-34804 Don't run secondary_reads_timestamp_visibility on storage engines that don't support snapshot reads
Branch: master
https://github.com/mongodb/mongo/commit/25202711c79bb4da07dd2ec320b8350db2fd2d7d

Comment by Eric Milkie [ 02/May/18 ]

We can use supportsSnapshotReadConcern() in global_snapshot_reads_helpers.js for this.

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