Only get the default write concern from ReplSetConfig if no write concern is specified

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2019-10-07
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, we call getGetLastErrorDefault every time extractWriteConcern is called even though a write concern is already specified. For {w: majority}, this means that we have an unnecessary serialization point in extractWriteConcern. We can change this to be on-demand to avoid locking the ReplicationCoordinator mutex.

            Assignee:
            Lingzhi Deng
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: