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

When catchUpTimeoutMillis is 0, we should skip doing catchup entirely

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.7, 3.5.10
    • Replication
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-06-19, Repl 2017-07-10
    • 0

    Description

      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.

      Attachments

        Activity

          People

            siyuan.zhou@mongodb.com Siyuan Zhou
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: