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

Metadata consistency checker must look for additional catalog inconsistencies

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: Catalog
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-09-02, CAR Team 2024-09-16, CAR Team 2024-09-30, CAR Team 2024-10-14
    • 2

      The metadata consistency checker is currently invoking $listCatalog on each shard and checking that a subset of the output is matching (the projected options).

      Since $listCatalog is returning the whole catalog entry that also includes additional info other than the fields we're currently projececting, we should rather identify the subset of fields that must not be projected and compare all other fields in order to spot inconsistencies.

      This would help us find issues as the one described in SERVER-90243: $listCatalog is returning the fields that are inconsistent, but we are never taking them into consideration in the consistency checker since they're not projected.

            Assignee:
            joan.bruguera-mico@mongodb.com Joan Bruguera Micó
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: