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

3.6 drivers fail to communicate with 3.6 sharded clusters running at FCV 3.4

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker - P1
    • Resolution: Fixed
    • 3.6.0
    • 3.6.4
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2018-03-26

    Description

      In 3.6 the MongoDB drivers added implicit support for sessions, which is triggered by the presence of the logicalSessionTimeoutMinutes field in the isMaster response.

      In 3.6, MongoS will always set its internal FCV to 3.6, regardless of the FCV of the shards and as a result it will always report logicalSessionTimeoutMinutes in the isMaster response. This, combined with the drivers' spec means that the driver will always send session information, regardless of the FCV version of the shards.

      Shards, which are at FCV 3.4 will reject any requests which contain session information and this essentially means that 3.6 drivers cannot be used to talk to a cluster which is at FCV 3.4.

      Attachments

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: