Skip the checkMetadataConsistency check in add_shard_refurbish.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1022
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • ClusterScalability 31Aug-14Sep
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The afterEach hook's ShardingTest.stop({skipValidation: true}) call still unconditionally runs checkMetadataConsistency(), which is not gated by skipValidation. This test deliberately stops/restarts the replica set and mongos mid-test, so by the time checkMetadataConsistency opens its own fresh connection to mongos, the process can already have exited, causing a spurious connection-refused failure in cleanup rather than a real test failure. 

            Assignee:
            Nandini Bhartiya
            Reporter:
            Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: