Do not take the replication coordinator mutex for all reads and writes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2026-02-16
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For reads, we take the mutex here: https://github.com/10gen/mongo/blob/eb44e53e46ca4beed28f8f29806771f3e68847df/src/mongo/db/service_entry_point_shard_role.cpp#L323-L345

      To include some replication metadata in the response.

      We also take it for writes.

      To reduce mutex contention, we should see if we can avoid taking it for every operation. 

            Assignee:
            Unassigned
            Reporter:
            Indy Prentice
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: