[SERVER-56696] Move cluster topology change notifications out of the change stream pipeline Created: 06/May/21  Updated: 29/Oct/23  Resolved: 20/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Bernard Gorman Assignee: Rishab Joshi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Query Execution 2021-05-17, Query Execution 2021-05-31
Participants:

 Description   

Currently, when a collection migrates to a new shard, an event is generated that passes through the pipeline to the mongoS, where it is consumed by the DocumentSourceUpdateOnAddShard stage. But when we start pushing down user-defined $match filters to the shard, we can no longer guarantee that the event will make it as far as DSUOAS, and migration events may therefore be missed.

We should move our handling of the kNewShardDetected event out of the change stream pipeline.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 20/May/21 ]

Author:

{'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}

Message: SERVER-56696: Introduce a new change stream stage to handle the topology
change event.
Branch: master
https://github.com/mongodb/mongo/commit/e53e42046e8e25f4cf9b6ffa68c71c2add8ae793

Generated at Thu Feb 08 05:39:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.