[SERVER-32686] Test snapshot isolation for {batchSize: 0} cursors Created: 12/Jan/18  Updated: 07/Mar/18  Resolved: 07/Mar/18

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

Type: Task Priority: Major - P3
Reporter: James Wahlin Assignee: James Wahlin
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-33698 batchSize:0 snapshot reads must alloc... Closed
Sprint: Storage 2018-01-29, Storage NYC 2018-03-12
Participants:

 Comments   
Comment by James Wahlin [ 02/Mar/18 ]

Narrowing scope of this ticket to address a gap in testing for batchSize: 0 cursors. We will add a test to both to snapshot_reads.js and read_concern_snapshot_yielding.js.

The only other gap we have identified is to test snapshot isolation during secondary snapshot reads. This will be addressed under SERVER-33580, once lock stashing no longer blocks replication on secondaries, being handled by SERVER-20328.

Comment by Tess Avitabile (Inactive) [ 26/Feb/18 ]

Some work has been done to extend read_concern_snapshot_yielding.js.

Comment by James Wahlin [ 16/Feb/18 ]

Repurposing again as SERVER-33223 will handle both stash creation and integration.

This ticket will be used to extend the snapshot_reads.js test to confirm snapshot isolation when:

  1. The snapshot read is at an interrupt point
  2. A write is performed that would show up as part of the result set if readConcern was local
Comment by James Wahlin [ 09/Feb/18 ]

Repurposing this ticket for integration of the snapshot stash for snapshot reads, being built under SERVER-33223.

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