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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2021-10-18
    • 136
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Benety Goh
            Reporter:
            Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: