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

CheckMetadataConsistency may fail to detect a RoutingTableRangeOverlap inconsistency (and return a ConflictingOperationInProgress error instead).

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-03-18

      SERVER-76293 introduced a new consistency check called checkCollectionOptionsConsistencyAcrossShards, which launches an aggregation from the primary shard of the collection being processed across the cluster.

      Such an aggregation requires a consistent and up-to-date routing table to be successfully performed, but it might face a situation where:

      • the routing table is in a corrupted state (due to an overlap between contiguous ranges)
      • the routing information cached on the primary shard is stale (so that such inconsistency goes undetected by the dedicated check that runs just before checkCollectionOptionsConsistencyAcrossShards).

      When this happens, the corrupted routing table causes checkCollectionOptionsConsistencyAcrossShards to consistently return a ConflictingOperationInProgress error (caused by the impossibility of installing the refreshed routing information on the primary shard cache).

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

              Created:
              Updated:
              Resolved: