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

Writing last vote to "local.replset.election" should not acquire PBWM lock

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0-rc0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Execution Team 2021-10-18
    • Linked BF Score:
      40

      Description

      When a replica set node persists the last response to replSetRequestVotes to the local.replset.election, it currently acquires the PBWM lock as part of the collection lock acquisition. This is unnecessary and could affect availability when the node is having issues during oplog application.

      The node can opt out of acquiring the PBWM lock using the ShouldNotConflictWithSecondaryBatchApplicationBlock.

      This issue was previously raised (see comment) as part of SERVER-48398.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              benety.goh Benety Goh
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: