restartAllConfigServers/restartAllShards should stop all config servers automatically

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      restartAllConfigServers as part of the ShardingTest API should stop all servers. As of now, the user has to call stopAllConfigServers before using this function. This leads to inconsistencies because restartAllMongos stops the Mongos's as part of the restartMongos function. The API should be consistent.

      If the user of the API calls restartAllConfigServers with calling stopAllConfigServers, there is an error can't start mongod, port 20040 already in use. This is unexpected behavior (would expect calling restartAllConfigServers to also stop them all)

            Assignee:
            Unassigned
            Reporter:
            Jada Lilleboe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: