Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19
-
46
Description
According to the new session catalog concurrency control design, all session users will be required to check-out the session in order to use anything on it. This ticket is about implementing this functionality as agreed in the associated design.
Attachments
Issue Links
- depends on
-
SERVER-36799 Move transaction related functionality from Session into TransactionParticipant
-
- Closed
-
-
SERVER-37711 Revert the `ReplicationStateTransitionLockGuard` functionality
-
- Closed
-
-
SERVER-37794 Introduce ability to specify interruptible failpoints
-
- Closed
-
-
SERVER-37689 Make recovery from query yield interruptible
-
- Closed
-
- is duplicated by
-
SERVER-37160 Coverity analysis defect 105017: Dereference null return value
-
- Closed
-
-
SERVER-37901 Two subsequent invalidations due to writes on the same session one after the other do not synchronize with each other
-
- Closed
-
-
SERVER-35909 Create SessionLocker that checks for active transactions automatically
-
- Closed
-
- is related to
-
SERVER-37900 Add ErrorCodes.Interrupted to error codes in snapshot_read_utils.js
-
- Closed
-