AsyncResultsMerger high‑water mark can move backwards when resuming all‑databases change stream v2 from a change event resume token

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • QE 2026-03-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The following tests started failing when the new shard targeter for ALL DATABASES change streams got merged:

      jstests/change_streams/whole_cluster_resumability.js

      jstests/change_streams/whole_cluster_metadata_notifications.js

      jstests/change_streams/apply_ops_resumability.js 

      jstests/change_streams/change_stream_pre_image_lookup_whole_db_whole_cluster.js 

      see for example here for error logs and stack traces: https://parsley.corp.mongodb.com/test/mongodb_mongo_master_rhel8_debug_aubsan_all_feature_flags_change_streams_multi_stmt_txn_mongos_passthrough_v2_69cbb16934e521284fff74c265bc1da959cf2827_26_03_12_15_12_49/0/1b5c04b6e799955474615863963e7d68?bookmarks=0,822,999&shareLine=822

            Assignee:
            Jan Steemann
            Reporter:
            Lyublena Antova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: