When catchUpTimeoutMillis is 0, we should skip doing catchup entirely

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.4.7, 3.5.10
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-06-19, Repl 2017-07-10
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently if catchUpTimeoutMillis is 0, we enter primary catchup mode and set a timeout to fire immediately. This is unnecessary and confusing; under some conditions the system can enter primary catchup mode and actually catch up before the "immediate" timeout fires, due to locking and scheduling vagaries.

            Assignee:
            Siyuan Zhou
            Reporter:
            Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: