Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11551

New 3.4 replica set with shardsvr option reports FCV as 3.2 until added to cluster

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor - P4 Minor - P4
    • Server_Docs_20231030
    • None
    • Server
    • None

    Description

      3.4 doc page on Backwards Incompatible Features says that new deployments default to FCV 3.4. There is a case where they do not.

      That case is when you deploy a brand new 3.4 replica set in preparation for adding it to a sharded cluster, in other words, you have the sharding.clusterRole: shardsvr option set. In this case, the FCV is reported as "3.2" until the replica set is added to the sharded cluster, at which point it will be set to the FCV of the sharded cluster as a whole. See SERVER-34342 for details.

      This probably applies to 3.6 also but I have not tested that.

      Attachments

        Activity

          People

            Unassigned Unassigned
            spencer.brown@mongodb.com Spencer Brown
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              1 year, 14 weeks, 2 days ago