Fix printShardingStatus.js in sharding_clustered_collections suite

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The test copies config database collections including options to a standalone mongod for verifying printShardingStatus() output. The config.chunks collection on the config server has recordIdsReplicated: true in all feature flags variant. When this option is passed to the mongod's createCollection along with clusterdIndex set to true in the suite the server rejects the combination as incompatible.
      The underlying issue is that config.chunks is created on the config server through an internal path (sharding_util.cpp:createIndexOnCollection) that bypasses the clusterAllCollectionsByDefault failpoint, so it gets recordIdsReplicated: true instead of being clustered.

      The fix should remove this option before sending createCollection command.

            Assignee:
            Abdul Qadeer
            Reporter:
            Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: