Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 8.0.5, 7.0.20
Affects Version/s: 7.3.0-rc0
Component/s: Internal Code
Labels:
None

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v8.0, v7.0
Sprint:
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
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Adi Agrawal (Inactive)
Reporter:: Mindaugas Malinauskas
Participants:: Adi Agrawal, Githook User, Mindaugas Malinauskas
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jan 11 2024 05:42:30 PM UTC
Updated:: Apr 09 2025 09:04:18 PM UTC
Resolved:: Nov 21 2024 06:34:06 PM UTC
Confidence Status Last Update:: 12/Nov/24 4:54 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates