Avoid increasing connection count to passive secondaries with matchPrimaryNode

XMLWordPrintableJSON

    • Fully Compatible
    • v4.2
    • Service Arch 2019-08-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      the matchPrimaryNode mode for the sharding connection pool currently spools as many connections to priority 0 nodes as to electable nodes. This isn't desirable, because those nodes won't become primary (so we don't need to stock as many connections to them).

      We have this information from isMaster (in the form of the "passive" and "passives" fields), so should expose it in the rsm + use it for matchPrimaryNode

              Assignee:
              Benjamin Caimano (Inactive)
              Reporter:
              Mira Carey
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: