-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Repl 2018-10-08, Repl 2018-10-22, Repl 2018-11-05, Repl 2018-11-19, Repl 2018-12-03
To allow state transitions when there are prepared transactions holding on to locks. Stepdown was handled already in SERVER-35870
- depends on
-
SERVER-35870 Temporarily release locks on replica set stepdown
- Closed
-
SERVER-37569 prohibit MapReduce on sessions with txnNumbers
- Closed
-
SERVER-37945 Replace the Global X lock with a ReplicationStateTransitionLockGuard wherever we acquire it for a state transition
- Closed
-
SERVER-37986 make a new ReplicationCoordinator inner class “ReadWriteAbility” that encapsulates “can accept writes” and “can serve reads” bools
- Closed
-
SERVER-37987 Use finer grained locks for on step up reads and writes
- Closed
-
SERVER-37989 Create new ReplicationStateTransitionLock resourceId and acquire it in mode IX when acquiring the GlobalLock in any intent mode.
- Closed
-
SERVER-37990 Replace locking requirements in “ReadWriteAbility” with new semantics around ReplicationStateTransitionLock
- Closed
-
SERVER-37991 Release ReplicationStateTransitionLock on prepare and reacquire it on commit and abort
- Closed
-
SERVER-38162 Acquire ReplicationStateTransitionLock on shutdown in mode X
- Closed
- duplicates
-
SERVER-38161 Test that prepared transactions can span all state transitions
- Closed
- is related to
-
SERVER-27534 All writing operations must fail if the term changes
- Closed
-
SERVER-37574 Force reconfig should kill user operations
- Closed
-
SERVER-37988 recover locks on step up at the beginning of the state transition rather than at the end
- Closed
- related to
-
SERVER-37711 Revert the `ReplicationStateTransitionLockGuard` functionality
- Closed
-
SERVER-38163 Remove enqueue abilities from GlobalLock
- Closed