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

Set secondaryCatchUpPeriodSecs smaller when requesting remote primary stepdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.13, 3.4.3, 3.5.4
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4, v3.2
    • Sprint:
      Repl 2017-03-06
    • Linked BF Score:
      0

      Description

      We need to change the stepdown commands sent to a lower-priority primary to set secondaryCatchUpPeriodSecs to a smaller number than heartbeat interval. Otherwise, a series of blocked stepdown commands will starve the stepdown via heartbeat waiting on the global lock.

      This is a quick fix before we fix SERVER-27911.

        Attachments

          Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26747 replSetStepDown should wait for last write to commit

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: