-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
v4.2
-
Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09
The kCommittingWithPrepare and kCommittingWithoutPrepare transaction states were originally added because needed to release the TransactionParticipant mutex before calling into the OpObserver, and a concurrent operation could modify the TransactionParticipant state while the mutex was not held. After SERVER-38810, however, the session must be checked out in order to modify TransactionParticipant state, so the kCommittingWithPrepare and kCommittingWithoutPrepare transaction states are likely unnecessary.
- is related to
-
SERVER-38810 Use the Client mutex or the SessionCatalog mutex for concurrency control of the TransactionParticipant
- Closed