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

when adding arbiter the PRIMARY fails to SECONDARY immediately

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 1.6.3, 1.7.0
    • Affects Version/s: 1.6.0
    • Component/s: Replication
    • None
    • Environment:
      linux x64
    • ALL

      When adding arbiter, immediately the PRIMARY goes to SECONDARY.

      Steps:

      • create new 2 node cluster.
        config=
        Unknown macro: {"_id"}

        rs.initiate(config)

      • add arbiter
        rs.addArb("al05:27017");

      here is a log of the action:
      http://gist.github.com/510474

            Assignee:
            dwight@mongodb.com Dwight Merriman
            Reporter:
            kgorman Kenny Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: