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

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

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1
    • None
    • Replication
    • None
    • Fully Compatible
    • Repl 2019-10-07

    Description

      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.

      Attachments

        Activity

          People

            lingzhi.deng@mongodb.com Lingzhi Deng
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: