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

Direct connection insert race with catalog refresh in drop_collection_if_uuid_not_matching.js

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • Hide

      1. Apply attached patch
      2. Run python buildscripts/resmoke.py run --suites=sharding jstests/sharding/drop_collection_if_uuid_not_matching.js --log=file --runAllFeatureFlagTests

      Show
      1. Apply attached patch 2. Run python buildscripts/resmoke.py run --suites=sharding jstests/sharding/drop_collection_if_uuid_not_matching.js --log=file --runAllFeatureFlagTests
    • CAR Team 2024-04-01
    • 20

      SERVER-80135 make shards refresh asynchronously the collection metadata after a shardCollection. In drop_collection_if_uuid_not_matching.js a direct connection to the shard is established and after a shardCollection an insert command is executed, which races with the refresh. If the insert wins, then the test will fail with a StaleConfig error.

      We could fix this by making the test to wait for the refresh to happen, or force a refresh after the shardCollection.

        1. BF-32229.patch
          3 kB

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: