-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v8.0
-
CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10
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
-
-
- Backlog
-
- is related to
-
SERVER-33090 $changeStream can fail if a shard was removed
-
- Backlog
-
-
-
- Backlog
-