[SERVER-1921] unable to add a shard when passive members are listed on addshard command Created: 11/Oct/10  Updated: 12/Jul/16  Resolved: 11/Oct/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 1.7.0
Fix Version/s: 1.7.2

Type: Bug Priority: Major - P3
Reporter: Alvin Richards (Inactive) 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   

Problem:
When adding a shard, if the passive members of the replset are included, then the addshard command fails

db.runCommand(

{ addshard : "set3/rs3a:27018,rs3b:27018,rs3c:27018,rs3d:27018", maxSize: 409600, name : "shard3" }

);

{
"ok" : 0,
"errmsg" : "host rs3c:27018 does not belong to replica set set3"
}

Workaround:
Only include the active members in the addshard command, and the addshard will succeed

Reproduce:

  • create a 3 member replset
  • set two nodes with Priority 1 and one with Priority 0
  • try the addshard command with all three nodes
  • get the failure message

Business Case:
Ease of use



 Comments   
Comment by Kristina Chodorow (Inactive) [ 11/Oct/10 ]

Fixed by http://github.com/mongodb/mongo/commit/61ab457c34cf1ddd0ece169eff1053ae9c082883.

Generated at Thu Feb 08 02:58:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.