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

When catchUpTimeoutMillis is 0, we should skip doing catchup entirely

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.7, 3.5.10
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2017-06-19, Repl 2017-07-10
    • Linked BF Score:
      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

            Assignee:
            siyuan.zhou Siyuan Zhou
            Reporter:
            matthew.russotto Matthew Russotto
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: