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

Change shutdown/stepdown to block writes and wait until at least 1 electable secondary is fully caught up

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.7.8
    • Affects Version/s: None
    • Component/s: Concurrency, Replication
    • Labels:
      None
    • Minor Change

      Currently shutdown starts by waiting for at least 1 secondary to be within 10 seconds of its optime (while still accepting new writes), then it steps down, then it waits again for a secondary to be completely caught up before shutting down. Once the new concurrency system allows it, we should start by blocking new incoming writes while retaining PRIMARY status, and wait until a secondary is completely caught up before stepping down and then shutting down.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: