[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: |
|
||||
| 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: |
| Comment by Eric Milkie [ 02/May/18 ] |
|
We can use supportsSnapshotReadConcern() in global_snapshot_reads_helpers.js for this. |