Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-6115

clarifications for https://docs.mongodb.org/manual/reference/command/replSetStepDown/

    XMLWordPrintableJSON

Details

    Description

      As discussed with milkie, this page can use more clarity w.r.t. expected behaviors of secondaries after the primary has stepped down via force:true. IIRC:

      • In 3.0 (and earlier) a secondary will not run for the election unless it's the freshest. So if you force a stepdown of your primary, and your secondaries are still catching up, you will not have a primary until the freeze timeout expires or until one of the secondaries catches up and runs for the election. I.e. rollbacks are unlikely.
      • In 3.2 under certain circumstances a stale secondary might get elected after a forced stepdown, so rollbacks are more likely.. However, w:majority writes will not be rolled back.

      Additionally, if I understood milkie correctly, the replSetStepDown command takes a global lock for the duration of secondaryCatchUpPeriodSecs, and that can result in queueing and potentially in accumulating connections on the primary.

      Attachments

        Activity

          People

            kay.kim@mongodb.com Kay Kim (Inactive)
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              1 year, 14 weeks, 1 day ago