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

secondaryCatchUpPeriodSecs of rs.stepDown() doesn't seem to work

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.9
    • Component/s: Replication
    • None
    • ALL
    • Hide

      Just run below command. and compare the elapsed seconds to elect new primary.

      rs.stepDown(100, 90)
      rs.stepDown(100,5)

      Show
      Just run below command. and compare the elapsed seconds to elect new primary. rs.stepDown(100, 90) rs.stepDown(100,5)

      I've run rs.stepDown(long, int) command several times with different integer paramter.
      But looks like period to elect new primary is nothing to do with secondaryCatchUpPeriodSecs and replSetStepDown parameters.

      And one more thing is that primary/secondary swithing by changing member priority value doesn't waiting replication sync so this method make rollback but rs.stepDown is not.
      Is there any difference between above two method ? (I can't find any difference of two method in manual.)

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            sunguck.lee@gmail.com 아나 하리
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: