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

[SBE] Fix various $changeStream tests timing out

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Querying, Sharding
    • Labels:
      None

      Description

      Many tests in the SBE build variant that exercise sharding fail with

      [js_test:lookup_change_stream_post_image_compound_shard_key] assert.soon failed: () => changeStream.hasNext() The hang analyzer is automatically called in assert.soon functions. If you are *expecting* assert.soon to possibly fail, call assert.soon with {runHangAnalyzer: f
      

      A non-exhaustive list of these tests in jstests/sharding/:

      • jstests/sharding/change_stream_chunk_migration.js
      • jstests/sharding/change_stream_empty_apply_ops.js
      • jstests/sharding/change_stream_metadata_notifications.js
      • jstests/sharding/change_stream_transaction_sharded.js
      • jstests/sharding/change_streams_shards_start_in_sync.js
      • jstests/sharding/change_streams_unsharded_becomes_sharded.js
      • jstests/sharding/change_streams/lookup_change_stream_post_image_compound_shard_key.js
      • jstests/sharding/change_streams/resume_change_stream_on_subset_of_shards.js
      • jstests/sharding/change_streams/lookup_change_stream_post_image_hashed_shard_key.js
      • jstests/sharding/change_streams_delete_in_txn_produces_correct_doc_key.js
      • jstests/sharding/change_streams/lookup_change_stream_post_image_id_shard_key.js
      • jstests/sharding/change_stream_read_preference.js
      • jstests/sharding/change_stream_enforce_max_time_ms_on_mongos.js
      • jstests/sharding/change_streams_unsharded_update_resume.js
      • jstests/sharding/change_stream_update_lookup_collation.js
      • jstests/sharding/change_stream_error_label.js
      • jstests/sharding/change_streams_new_shard_new_database.js
      • jstests/sharding/change_stream_resume_from_different_mongos.js
      • jstests/sharding/change_streams/resume_change_stream.js
      • jstests/sharding/change_streams_update_lookup_shard_metadata_missing.js
      • jstests/sharding/change_stream_update_lookup_read_concern.js
      • jstests/sharding/change_streams/resume_change_stream_from_stale_mongos.js
      • jstests/sharding/change_streams_primary_shard_unaware.js
      • jstests/sharding/change_streams.js
      • jstests/sharding/change_streams_whole_db.js
      • jstests/sharding/change_stream_lookup_single_shard_cluster.js
      • jstests/sharding/change_stream_shard_failover.js

      This ticket also encompasses assert.soon() failures related to change streams in the multiversion suite:

      • jstests/multiVersion/genericChangeStreams/change_streams_read_oplog_after_downgrade.js (task)
      • jstests/multiVersion/genericChangeStreams/change_streams_multi_version_cluster.js (task)

      See also SERVER-55076

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-query-execution Backlog - Query Execution
              Reporter:
              kyle.suarez Kyle Suarez
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: