Explore introducing a random sampling hook for timestamp consistency of multikeyness

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-06-08, CAR Team 2026-06-22
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Having multikeyness timestamp consistency checks on existing suites might help uncover missed edge cases. However, an exhaustive verification (e.g. oplog walk) is probably too slow.

      A potential solution might be to randomly sample existing collections and indexes, and verify primary and secondary nodes agree on the multikeyness using same timestamp.

            Assignee:
            Yujin Kang Park
            Reporter:
            Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: