-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Labels:None
Description
Link: https://docs.mongodb.com/manual/reference/replica-states/index.html#replstate.STARTUP2
This states:
> Each member of a replica set enters the STARTUP2 state as soon as mongod finishes loading that member’s configuration, at which time it becomes an active member of the replica set and is eligible to vote.
However arbiters seem to go straight from STARTUP->ARBITER as per these log lines:
2020-06-04T13:35:43.959+0200 I REPL [replexec-0] New replica set config in use: { _id: "replset", version: 1, protocolVersion: 1, writeConcernMajorityJournalDefault: true, members: [ { _id: 0, host: "localhost:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 1, host: "localhost:27018", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "localhost:27019", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 3, host: "localhost:27020", arbiterOnly: true, buildIndexes: true, hidden: false, priority: 0.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: ObjectId('5ed8dbd311e635ef4886958b') } } 2020-06-04T13:35:43.959+0200 I REPL [replexec-0] This node is localhost:27020 in the config 2020-06-04T13:35:43.959+0200 I REPL [replexec-0] transition to ARBITER from STARTUP
Tested in v4.2 but probably applies to all recent versions.
Maybe a change to "Each data-bearing member of a replica set enters..." would be sufficient.