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

Add info re: primary catchup to architecture guide

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

      Let's add information on when primary catch up terminates. By default the catch up timeout is set to -1 which means we have an infinite timeout. But in practice we don't hit this. We should explain why that's the case.

      We should also break down the steps of recalculating the target opTime each time a heartbeat is received and also the different situations in which catch up can be aborted.

            Assignee:
            Unassigned Unassigned
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: