rs.reconfig, rs.add etc commands shouldn't have to be set on a master

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Shell
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            DO NOT USE - Backlog - Platform Team
            Reporter:
            Arin Sarkissian
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: