Check Metadata Consistency can segfault if the collection disappears during UUID check

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • None
    • 3
    • TBD
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      During check metadata consistency, we use a helper to get the number of documents in a collection for a couple of inconsistencies. Because this helper doesn't check that the collection exists after acquiring the AutoGetCollection, this can segfault if the collection disappears out from under the CMC command.

      This is quite difficult to hit, though, since it would require either the UUID on the shard catalog and locally to differ or the collection to exist outside the dbPrimary shard (and not be tracked) in addition to the collection disappearing at the correct time during the CMC command.

              Assignee:
              Unassigned
              Reporter:
              Allison Easton
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: