[SERVER-3453] db.isMaster() reporting true for both arbiterOnly and passive (under certain configs) Created: 20/Jul/11  Updated: 12/Jul/16  Resolved: 29/Jul/11

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 1.9.0
Fix Version/s: 1.9.2

Type: Bug Priority: Minor - P4
Reporter: Robert Stam Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

When a replica set member is configured with both arbiterOnly and priority = 0 (admittedly a weird combination), then db.isMaster() on the arbiter reports true for both arbiterOnly and passive.

Here's the replica set config:

myset:PRIMARY> rs.conf()
{
"_id" : "myset",
"version" : 1,
"members" : [

{ "_id" : 0, "host" : "Kilimanjaro:10001" }

,

{ "_id" : 1, "host" : "Kilimanjaro:10002" }

,

{ "_id" : 2, "host" : "Kilimanjaro:10003", "priority" : 0, "arbiterOnly" : true }

]
}
myset:PRIMARY>

Here's the result db.isMaster() on the arbiter:

myset:ARBITER> db.isMaster()
{
"setName" : "myset",
"ismaster" : false,
"secondary" : false,
"hosts" : [
"Kilimanjaro:10002",
"Kilimanjaro:10001"
],
"arbiters" : [
"Kilimanjaro:10003"
],
"primary" : "Kilimanjaro:10001",
"arbiterOnly" : true,
"passive" : true,
"maxBsonObjectSize" : 16777216,
"ok" : 1
}
myset:ARBITER>

The following four properties reported by db.isMaster() should probably be mutually exclusive:

ismaster
secondary
arbiterOnly
passive



 Comments   
Comment by auto [ 29/Jul/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: arbiters are not passive SERVER-3453

Conflicts:

jstests/replsets/replsetarb2.js
Branch: master
https://github.com/mongodb/mongo/commit/2035656b204c6cbcd04dc515a87d6c675373bf94

Generated at Thu Feb 08 03:03:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.