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

Set catchUpTimeoutMillis if catchup takeover is disabled

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: