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

Arbiter fails to respect priority in 2 read/write node 1 arbiter setup

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major - P3 Major - P3
    • None
    • 2.0.1, 2.0.2
    • Replication
    • Linux TELL02VMW01 2.6.32-37-server #81-Ubuntu SMP x86_64 GNU/Linux
    • Linux

    Description

      I've been trying to setup a simple replication system. 1 main mongo, 1 backup, and 1 arbiter.

      Unfortunately, firing it up lead to main being elected SECONDARY, and the backup being elected PRIMARY.

      Main priority set to 100, and backup a priority of 0, along with a slave delay of 3600.

      Downing backup leads to main being elected PRIMARY, but when backup is brought back on line, it resumes its spot as PRIMARY. Main then enters RECOVERING mode, and never recovers.

      hidden = true has no effect on this behaviour.

      More details including various config files:

      http://stackoverflow.com/questions/8858831/trying-to-setup-mongo-replication-but-end-up-with-two-secondary-members-and-no/8858940#8858940

      This was eventually solved by reinstalling all of the relevant servers.

      Attachments

        Activity

          People

            Unassigned Unassigned
            juwiley Justin Wiley
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: