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

Multiversion tests run with analyzeShardKey and _clusterQueryWithoutShardKey cmd not found

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v6.2
    • Sharding 2022-12-12
    • 153
    • 2

      In BF-27104 the following list of tests (not exhaustive) contain @requires_fcv_62 tag for analyzeShardKey command without the feature being enabled by default in v6.2:

       

      jstests/sharding/analyze_shard_key/cardinality_and_frequency_basic.js
      jstests/sharding/analyze_shard_key/configure_query_analyzer_persistence.js
      jstests/sharding/analyze_shard_key/persist_sampled_read_queries.js
      jstests/sharding/analyze_shard_key/persist_sampled_retryable_update_queries.js
      jstests/sharding/analyze_shard_key/persist_sampled_write_queries.js
      jstests/sharding/analyze_shard_key/sample_nested_agg_queries_unsharded.js
      jstests/sharding/analyze_shard_key/sample_rates.js 
      

      The feature itself is disabled currently in 6.2 and 6.3

      A temporary fix would be to change @requires_fcv_62 tag to @requires_fcv_63 in master branch until the feature is enabled. Similarly, the tag for tests using featureFlagUpdateOneWithoutShardKey feature flag should also be updated. Long term solution is to rely on the fix by SERVER-71467
       

            Assignee:
            abdul.qadeer@mongodb.com Abdul Qadeer
            Reporter:
            abdul.qadeer@mongodb.com Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: