[SERVER-34462] changeStreams will incorrectly notify for oplog entries generated by copying collections on movePrimary Created: 13/Apr/18 Updated: 31/Jul/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.4, 3.7.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | movePrimary, pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This is because the Cloner used by movePrimary does not mark these oplog entries as 'fromMigrate', the way the moveChunk protocol does. This is a pre-existing bug since 3.6, and would go away if we tracked unsharded collections and moved them through moveChunk rather than movePrimary. |
| Comments |
| Comment by Brett Nawrocki [ 09/Feb/23 ] |
|
We decided against addressing this as part of PM-3025 because solving the problems surrounding change streams piecemeal will introduce more distinct sets of behaviors that need to be kept in mind when considering historical versions. Instead, it will be left to PM-1941 to do a single pass addressing the outstanding issues. |
| Comment by Steve Tarzia [ 13/Dec/22 ] |
|
Assigning this back to sharding based on Max's comment. If there's a reason this should be on Query Execution, please let us know. |
| Comment by Max Hirschhorn [ 02/Nov/22 ] |
|
I expect this will be addressed as part of the Online movePrimary project (PM-3025). |
| Comment by Esha Maharishi (Inactive) [ 13/Apr/18 ] |