[SERVER-34705] Whole-DB or whole-cluster change streams may not provide a total ordering if resumed after a drop Created: 26/Apr/18 Updated: 29/Oct/23 Resolved: 29/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc2, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Nicholas Zolnierz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Sprint: | Query 2018-05-21, Query 2018-06-04 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This is a more general case than the one described in Consider the following sequence of events:
One suggested approach for this problem is to remember the shard key that was given to us in the resume token when we resume, allowing us to populate the shard key for the insert entry. This will solve this scenario, but will not solve the scenarios described in |
| Comments |
| Comment by Githook User [ 04/Jun/18 ] |
|
Author: {'username': 'nzolnierzmdb', 'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com'}Message: (cherry picked from commit 55f4dbf94a1cce9d8642af9bba9ac4cc77627293) |
| Comment by Githook User [ 29/May/18 ] |
|
Author: {'username': 'nzolnierzmdb', 'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com'}Message: |