[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: |
|
||||||||||||
| 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. |