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

When catchUpTimeoutMillis is 0, we should skip doing catchup entirely

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 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

      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@mongodb.com Siyuan Zhou
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: