[SERVER-72099] Writes done as part of movePrimary should not generate change stream events Created: 14/Dec/22  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-34424 a changeStream on a database will inc... Open
is related to SERVER-34462 changeStreams will incorrectly notify... Open
Assigned Teams:
Cluster Scalability
Participants:

 Description   

Both the cloning of the data (recipient side) and the purging of stale data (donor side) of the the movePrimary command generate useless change stream events.

The generation of these events on cloning phase could be addressed in the context of the Online movePrimary project (PM-3025), while these on cleaning stale data in the context of making the movePrimary command resilient.


Generated at Thu Feb 08 06:20:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.