RoutingContext fails to identify timeseries collection when buckets namespace cache is stale after dropDatabase + shardCollection on different mongos

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2026-03-02, CAR Team 2026-03-16
    • 0
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The test can fail (inconsistently) when run on the sharded_collections_jscore_passthrough_with_config_transitions_and_add_remove_shards 

      patch https://parsley.corp.mongodb.com/test/mongodb_mongo_master_enterprise_amazon_linux2023_arm64_all_feature_flags_sharded_collections_jscore_passthrough_with_config_transitions_and_add_remove_shard_3_linux_enterprise_patch_53022004e527dca28c5288d1641dda514b390ece_698c79601e7fae00075eac0d_26_02_11_12_43_27/0/8416e10aa4013c86d772b0af165a9bf0?bookmarks=0,607&selectedLineRange=L451-L601&shareLine=0

      Note that this happened after SERVER-118981 where the dispatching logic has been moved from `runCommand` to `_runCommandImpl` which implies every command that runs as part of any override of the runCommand in the suite's hook is also dispatched

      The patch seem to expose an internal transaction error that shouldn't leak when a router is stale.

            Assignee:
            Unassigned
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: