audit wire version checks to ensure we reject or close connections from clients with binary versions that are too old

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.5.13
    • Component/s: Sharding
    • None
    • Sharding 2017-10-23
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket should update the places where we check a client's wire protocol version to

      • decide what maxWireVersion to send back in the isMaster handshake (to make the client fail to connect if it's too old)
      • decide whether to close client connections from clients that are too old
      • decide whether a shard is too old to add to a cluster

      particularly to check "in any state other than fully downgraded to 3.4" rather than just checking "in 3.6."

            Assignee:
            Esha Maharishi (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: