Two Primaries if Replica Set Heartbeats Fail in One Direction: "Old" Primary doesn't relinquish.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.5
    • Component/s: Replication
    • None
    • Environment:
      Three Node Replica Set (2 data bearing, 1 arbiter)
    • ALL
    • Hide

      1. Setup three node replica set (2 data bearing, 1 arbiter) and run mongod with '--maxConns 5'.
      2. Ensure that the primary (A) has an replica set member configuration _id less than the secondary (B).
      3. Use mongo shell to connect repeatedly to A such that replica set heartbeats from the arbiter or B fail to connect to A.

      Show
      1. Setup three node replica set (2 data bearing, 1 arbiter) and run mongod with ' --maxConns 5 '. 2. Ensure that the primary (A) has an replica set member configuration _id less than the secondary (B). 3. Use mongo shell to connect repeatedly to A such that replica set heartbeats from the arbiter or B fail to connect to A.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Because of this line, it's possible for two primaries to exist simultaneously if the "old" primary has an _id less than the "new" primary. "old" primary will stay in PRIMARY state until restarted.

            Assignee:
            Unassigned
            Reporter:
            Stephen Lee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: