[SERVER-4690] rs.reconfig, rs.add etc commands shouldn't have to be set on a master Created: 16/Jan/12  Updated: 05/Apr/17  Resolved: 27/Jan/17

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

Type: New Feature Priority: Major - P3
Reporter: Arin Sarkissian Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

when reconfiguring a replica set the docs at http://www.mongodb.org/display/DOCS/Replica+Set+Tutorial say "the reconfig command must be sent to the current primary of the set."

why? That's stupid. The spirit of replica sets is that they "handle themselves" - they'll elect a master, keep up to date and all that other jazz. So from my perspective, most of the time, i don't care which node is currently the primary. I should be able to connect to any node thats up to reconfigure the set.

this is an "I'm lazy, please make administration easier" request. as it stands i have a wrapper script to do this - but for certain things like this that pop up over and over it would make sense to just build-in the functionality



 Comments   
Comment by Mira Carey [ 27/Jan/17 ]

When using the shell with mongodbi uri's pointed at a replica set, the shell will route commands to the current primary, which should take care of this for you.

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