In a distributed transaction, when the coordinator writes its commit decision, it takes global/db/collection locks to do so while the participant is also still holding the global lock. This can cause issues when combined with operations that take strong global locks, as seen in SERVER-65821. We should investigate ways to improve this behavior so that we can remove the workaround added in that ticket. One potential idea is to consolidate the participant and coordinator on the coordinating shard, so that they can make progress with a single set of resources.
- is depended on by
-
SERVER-79922 Investigate solutions to the fsync (lock:true) starvation scenario
-
- Backlog
-
-
SERVER-66342 Remove resourceIdFeatureCompatibilityVersion
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- related to
-
SERVER-65821 Deadlock during setFCV when there are prepared transactions that have not persisted commit/abort decision
-
- Closed
-
-
-
- Closed
-