Investigate NamespaceNotSharded error on explain of sharded timeseries concurrent with upgrade/downgrade

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 9.0.0-rc0
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2026-04-13
    • 馃煩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Investigate why the timeseries_buckets_write_explain.js test throws a NamespaceNotSharded error when running in the fcv_upgrade_downgrade_sharded_collections_jscore_passthrough suite with viewless timeseries upgrade downgrade.

      聽

      It appears that we do lookup CollectionRoutingInfo twice in the mongos and if the first one thinks the collection is sharded but the second one thinks it is unsharded (because of a concurrent viewless upgrade/downgrade) we throw a NamespaceNotSharded error here.

        1. repro-SERVER-122590.patch
          8 kB

            Assignee:
            Joan Bruguera Mic贸
            Reporter:
            Joan Bruguera Mic贸
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: