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

checkMetadataConsistency should return number of documents contained in unexpected collections

    • Catalog and Routing
    • Fully Compatible
    • v8.1, v8.0, v7.0
    • CAR Team 2025-05-12
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When the check metadata consistency command is spotting a misplaced collection or a collection uuid mismatch, it would be useful to also return the number of documents the collection contains.

      If the collection contains zero documents, the error message should explicitly state that it is safe to drop the collection via direct connection for remediating.

      This will make troubleshooting much easier for users that collections created unintentionally via direct connections or due to rolling index builds targeting all shards instead of only the ones owning data.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: