Reading and writing FCV is asymmetric in sharded clusters

    • Catalog and Routing
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      https://docs.mongodb.com/manual/reference/command/setFeatureCompatibilityVersion/ states that setting FCV is done on a mongos, but reading the FCV back on a mongos is not allowed.

      Writing:

      > For a sharded cluster, run the command on a mongos instance.

      Reading:

      > The operation is undefined on the mongos instances. For a sharded cluster that has access control enabled, to run the command against a member of the shard replica set, you must connect to the member as a shard local user.

      Why is mongos able to write FCV but not read it back?

              Assignee:
              Unassigned
              Reporter:
              Oleg Pudeyev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: