-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
As part of SERVER-59673 we've introduced a function that provided a collection name tells whether it is safe to not take the RSTL lock for it in collection_utils.h.
Initially this function will only contain the system.profile collection, but ideally it should have others inside. For example non-replicated collections could go there as long as they aren't used by the replication system.
We can't exclude all unreplicated collections from taking the RSTL lock because things like local.replset.election and local.replset.minvalid might not be safe for that. This ticket is to investigate further skipping RSTL acquisition for non-replicated collections when possible.
- depends on
-
SERVER-59673 Investigate better solutions for fixing the deadlock issue in profiling
- Closed
- is related to
-
SERVER-51100 Make dry-run elections write to lastVote like real elections do
- Blocked