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

Do not hold the replication executor mutex/lock while running isself

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • 3.0.0
    • Replication
    • Replication
    • ALL

    Description

      Currently when loading or validating a new config the isself check is run when holding the mutex/lock and it can lead to a dead lock or client/operation delays.

      We should instead schedule any long running IO, like the network request isself might make, of any lock.

      We may also want to audit the code to make sure no instance of this pattern exist, where we hold the mutex and issue network/disk work.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: