checkMetadataConsistency can send aggregations to lagged secondaries

ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v9.0, v8.0
    • CAR Team 2026-08-03, CAR Team 2026-08-17
    • 200
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Part of the checkMetadataConsistency process involves sending various aggregations to shards for cross-shard checking of information.

      However, these aggregations always end up with a readPreference of "secondaryPreferred" that means it can target lagged secondaries.

      As a result, these can result in false positives due to these lagged secondaries seeing a stale version of what's majority committed.

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: