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

4-node set with 2 arbiters can't elect primary

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.7.8
    • Affects Version/s: None
    • Component/s: Replication
    • ALL

      Built from master (hash 4bea2a9) with "scons --replication-implementation=impl", started 4 nodes on localhost. Initiated with two arbiters:

      > rs.initiate({_id: 'rs', members:[{_id:0, host: 'localhost:27017'}, {_id: 1, host:'localhost:27018'}, {_id: 2, host:'localhost:27019', arbiterOnly:true}, {_id: 3, host:'localhost:27020', arbiterOnly: true}]})
      { "ok" : 1 }
      

      After waiting a minute I still have two secondaries and two arbiters, no primary. localhost:27017 logs:

      2014-10-15T11:08:15.229-0400 I REPLSETS Standing for election
      2014-10-15T11:08:15.230-0400 I REPLSETS replSet info electSelf
      2014-10-15T11:08:15.230-0400 I REPLSETS replSet couldn't elect self, only received 2 votes, but needed at least 3
      2014-10-15T11:08:17.230-0400 I REPLSETS Standing for election
      ...
      

      And so on. The other secondary and both arbiters log continuously:

      2014-10-15T11:08:23.235-0400 I REPLSETS replSetElect voting yea for localhost:27017 (0)
      

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: