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

Set catchUpTimeoutMillis if catchup takeover is disabled

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Replication
    • Labels:
      None

      Description

      By default `catchUpTimeoutMillis` is set to -1 (infinity). If user disabled catchup takeover, without setting `catchUpTimeoutMillis`, and for whatever reason the primary is stuck in catchup/drain mode, then the system can freeze. Although users can manually issue `replSetAbortPrimaryCatchUp` command to abort catchup, this is still not good user experience because it involves user intervention and long unavailability window. We should either warn users when they disable catchup takeover without setting `catchUpTimeoutMillis` or alternatively fail the configuration when that happens.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              wenbin.zhu Wenbin Zhu
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: