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

[test-only] Exclude configsvr_commit_refine_collection_shard_key.js from stepdown suites

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc16
    • Affects Version/s: 7.1.0-rc0, 8.0.0-rc0, 7.3.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0, v5.0
    • CAR Team 2024-08-05
    • 0

      The configsvr_commit_refine_collection_shard_key.js test directly calls _configsvrCommitRefineCollectionShardKey on the config server to test the metadata changes happening when refining a shard key.

      While in production shards that call the command retry upon config server step-down, the test does not present any retry logic.

      It doesn't make much sense to make the test resilient to stepdowns, hence we should simply blacklist it from stepdown suites by applying the does_not_support_stepdowns tag.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: