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

The ChunkManager should raise a more explicit error when inconsistent metadata are fetched

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.3, v7.0
    • CAR Team 2024-04-01, CAR Team 2024-04-15, CAR Team 2024-04-29, CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16
    • 1

      The ChunkManager is part of the infrastructure supporting the caches of filtering metadata and routing information: when new metadata is fetched, it executes a few checks to verify their consistency, raising a ConflictingOperationInProgress when any violation is detected.

      Nevertheless, DDLs always modify the sharding catalog through transactions nowadays: if the ChunkManager retrieves an inconsistent state, it cannot be associated to an inflight DDL (and it is most likely the symptom of metadata being persistently corrupted).

            Assignee:
            adam.farkas@mongodb.com Wolfee Farkas
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: