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

Bring backing the default catchup timeout

    • Type: Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None

      Sometimes due to bugs or other issues the primary stepup can be stuck and catchup takeover does not work. The catchup takeover timeout is a more reliable way to bail out of this situation because it only relies on the stepping up node itself, but by default it is disabled due to the introduction of catchup takeover. Alternatively we can do PM-1039, but that is a larger effort than bring back the default catchup timeout.

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: