Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71536

Investigate if non-replicated collections can skip RSTL lock

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: