[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" : 2, "host" : "Kilimanjaro:10003", "priority" : 0, "arbiterOnly" : true } ] Here's the result db.isMaster() on the arbiter: myset:ARBITER> db.isMaster() The following four properties reported by db.isMaster() should probably be mutually exclusive: ismaster |
| 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 Conflicts: jstests/replsets/replsetarb2.js |