Router port on dedicated configsvr must only accept addShard or removeShard commands

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Dedicated config server can be run a on machine with limited hardware resources, and in an embedded router world, it will expose the router port making accept requests from clients, as a mongos can do. This will stress a dedicated config server that opened the router port only to add shards to the sharded cluster, as it is the right procedure to follow in an embedded router world.

      Goal

      We need to make the dedicated config server router port only accept addShard or removeShard commands in order to not stress the config server.

      References

      • No references.

      Estimation

      • User impact: Unavailable config server, making refreshes last too long.
      • Raw Estimation (man day): 5

              Assignee:
              [DO NOT USE] Backlog - Service Architecture
              Reporter:
              Pol Pinol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: