Investigate failure in server_status.js with CheckMetadataConsistencyInBackground

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v9.0
    • CAR Team 2026-07-20
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      jstests/concurrency/fsm_workloads/server_status/server_status.js is throwing an inconsistency for config.system.sessions where the DB primary shard has kUnowned flag due to invalid handling of the sessions collection during transitions:

      • during transition to dedicated the collection entry gets wiped out
      • however its collection entry specifically (due to the specifics of the sessions collection) can be recreated locally
      • this can result in the situation when a db primary (after transition back to embedded) holds local collection without collection entry for it  (e.g. sharding state is kUnkown) which is an invalid state.

      In order to fix this we're planning to make an exclusion for this collection in the CMC and the remove shard coordinator during transition to dedicated.

            Assignee:
            Rustam Gusein-zade
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: