Support different networks / nics for client & replication traffic

XMLWordPrintableJSON

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

      Problem:
      In order to scale network traffic for client connections and replication traffic, there are two options

      a) add a NIC
      b) swap out a 1Gig for a 10Gig Ethernet Card

      Case b) is already supported. However, to support case a) we would need to be able to specify different networks for
      – client connections (and failover of client connections)
      – replication connections

      Impact:

      This would impact
      – mongod would need to accept connections over more than a single interface
      – replSetInitate configuration would need the ability to specify a different ip/port for the replication traffic

      Other:
      Would need test cases for the client nic failover from the replication nic failover.

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Alvin Richards (Inactive)
            Votes:
            26 Vote for this issue
            Watchers:
            50 Start watching this issue

              Created:
              Updated:
              Resolved: