-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 7.3.0-rc0
-
Component/s: Internal Code
-
None
-
Query Execution
-
Fully Compatible
-
ALL
-
v8.0, v7.0
-
QE 2024-01-22, QE 2024-02-05, QE 2024-02-19, QE 2024-03-04, QE 2024-03-18, QE 2024-04-01, QE 2024-04-15, QE 2024-04-29, QE 2024-05-13, QE 2024-05-27, QE 2024-06-10, QE 2024-07-22, QE 2024-08-05, QE 2024-08-19, QE 2024-09-02, QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11, QE 2024-11-25
-
0
Change stream tests, including the ones that useĀ ChangeStreamTest do not recover from resumable change stream errors that may occur due to node being targeted interrupting "getMore" operations etc. These kind of errors may happen due to primary stepdowns (for example in sharding_csrs_continuous_config_stepdown suite) etc.
An example of such test is jstests/sharding/change_streams_unsharded_becomes_sharded.js.
- is related to
-
SERVER-97077 Ban changeStream tests from running in sharding_csrs_continuous_config_stepdown
- Closed
- related to
-
SERVER-84142 Fix lookup_change_stream_post_image_hashed_shard_key.js to retry the operations change stream operation when a step down is produced
- Closed