-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 1.8.2
-
Component/s: Replication, Sharding
-
None
-
ALL
Calling addShard fails when the shard has an arbiter.
rs1:PRIMARY> rs.status()
{
"set" : "rs1",
"date" : ISODate("2011-08-16T11:14:17Z"),
"myState" : 1,
"members" : [
{
"_id" : 0,
"name" : "192.168.10.114:27017",
"health" : 1,
"state" : 2,
"stateStr" : "SECONDARY",
"uptime" : 80051,
"optime" :
,
"optimeDate" :
ISODate("2011-08-11T09:50:00Z"),
"lastHeartbeat" :
ISODate("2011-08-16T11:14:17Z")
},
{
"_id" : 1,
"name" : "192.168.10.114:27018",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"optime" :
,
"optimeDate" :
ISODate("2011-08-11T09:50:00Z"),
"self" : true
},
{
"_id" : 2,
"name" : "192.168.10.114:27019",
"health" : 1,
"state" : 7,
"stateStr" : "ARBITER",
"uptime" : 79859,
"optime" :
,
"optimeDate" :
ISODate("1970-01-01T00:00:00Z"),
"lastHeartbeat" :
ISODate("2011-08-16T11:14:17Z")
}
],
"ok" : 1
}
> db.runCommand(
);
{
"ok" : 0,
"errmsg" : "host 192.168.10.114:27019 does not belong to
replica set as a non-passive memberrs1"
}