[SERVER-71536] Investigate if non-replicated collections can skip RSTL lock Created: 22/Nov/22  Updated: 05/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-59673 Investigate better solutions for fixi... Closed
Related
is related to SERVER-51100 Make dry-run elections write to lastV... Blocked
Assigned Teams:
Replication
Participants:

 Description   

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.


Generated at Thu Feb 08 06:19:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.