[TEST ONLY] check_metadata_consistency_basic.js fails to ignore known issues and might fail to split chunks

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0, 8.0.24
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2026-02-16, CAR Team 2026-03-02
    • 200
    • 1
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-117010 added a new test in core_sharding to run checkMetadataConsistency in all appropriate suites, however, it fails to consider currenty known issues that should be ignored, for example:

      • After SERVER-107762 there is a drop collection on config.system.sessions in the background that might generates inconsistencies
      • When running with shard stepdowns, an MalformedTimeseriesBucketsCollection could be generated that should also be ignored

      Additionally, the test is executing a split that might fail due to transient state. We should follow something similar to what the checkMetadataConsistency helper is doing, by ignoring some known issues and handling transient state.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: