Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.0.0-rc8
Affects Version/s: None
Component/s: None
Labels:
- auto-reverted
- server-rapid-response-resolved

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0
Sprint:
CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

As per today, change streams opened at pastPointInTime may silently miss events that were persisted on a shard that was removed from the cluster at pastPointInTime+x.

The same problem affects transitionToDedicatedConfigServer (which is built on top of movePrimary), but with a bigger impact. The scope of this ticket is to avoid event loss by rejecting the opening/resuming of change streams at a PIT that predates the commit of a removeShard.

is depended on by

SERVER-89220 Enable change_streams_multi_stmt_txn_mongos_passthrough_with_config_transitions.yml

Backlog

is related to

SERVER-33090 $changeStream can fail if a shard was removed

Backlog

SERVER-90751 Add an optional parameter to removeShard for peeking the draining state of the targeted replica set

Backlog

Assignee:: Paolo Polato
Reporter:: Paolo Polato
Participants:: Githook User, Paolo Polato, TPM Jira Automations Bot
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: May 09 2024 07:27:58 AM UTC
Updated:: Jun 10 2024 08:29:34 AM UTC
Resolved:: Jun 10 2024 08:24:32 AM UTC
Confidence Status Last Update:: 15/May/24 12:14 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates