[SERVER-33838] Replace setStashedCursor and hasStashedCursor with transaction state Created: 12/Mar/18  Updated: 27/Oct/23  Resolved: 24/Mar/18

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-33551 Track snapshot read transactions with... Closed
related to SERVER-33656 After initial snapshot read, only all... Closed
related to SERVER-34113 Remove all support for snapshot reads... Closed
Assigned Teams:
Replication
Sprint: Repl 2018-04-23
Participants:

 Description   

Multi-statement transaction shares the same resource stashing logic in sessions with local snapshot read. SERVER-33551 is the first step to unify them. If we consider snapshot read as autocommit: true read-only transaction, their life cycle management can be unified too. For example, SERVER-33656 can be fixed by the same logic that no command is allowed in a finished transaction.



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

This may not be important now that we are removing support for snapshot reads outside of transactions. For example, we could also remove setStashedCursor() as part of SERVER-34113.

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