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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 3.2.9
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      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)

      Description

      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.)

        Attachments

          Activity

            People

            Assignee:
            kelsey.schubert Kelsey T Schubert
            Reporter:
            matt.lee Matt SeongUck Lee
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: