[SERVER-33368] Add snapshot read testing for txnNumber change on Session::onMigrateBeginOnPrimary() call Created: 16/Feb/18  Updated: 06/Dec/22  Resolved: 26/Mar/18

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

Type: Task Priority: Major - P3
Reporter: James Wahlin Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-33367 Enforce a cursor is iterated in a tra... Closed
Duplicate
duplicates SERVER-34011 Concurrency between transaction and o... Closed
Assigned Teams:
Sharding
Participants:

 Description   

This should include both:

  1. In-flight snapshot reads with the Session checked out (include reads that will stash and reads that will not stash)
  2. txnNumber change for a Session that is not checked out but which has transaction resources stashed. Followed by a read on the given transaction.


 Comments   
Comment by Tess Avitabile (Inactive) [ 23/Mar/18 ]

Moving this to the Global Snapshot Reads epic. Snapshot reads will only be allowed in multi-statement transactions in 4.0, and multi-statement transactions will not be allowed on shard servers in 4.0.

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