Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42125

Avoid increasing connection count to passive secondaries with matchPrimaryNode

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Service Arch 2019-08-12

      Description

      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

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: