forceing a server to be primary prevents secondary from taking over if the forced primary fails.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.2.1
    • Component/s: Replication
    • None
    • Environment:
      mixed UBUNTU 12.04 SLES 11 64 bit
    • Linux
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      forcing a server to be primary as described in
      http://www.mongodb.org/display/DOCS/Forcing+a+Member+to+be+Primary
      using command
      db.adminCommand(

      {replSetStepDown:1000000, force:1}

      )

      and then stopping the daemon on the new master seems to prevent an election
      of a new primary at least for the 20 minutes I waited.

      It may be advisable to update the dos on the above page to warn admins that if they preformed this process the system may not recover from a failure.

            Assignee:
            Kristina Chodorow (Inactive)
            Reporter:
            Sean Mathews
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: