[SERVER-35917] Blacklists tests which use resumeAfter from the sharded collections change streams passthrough Created: 29/Jun/18 Updated: 29/Oct/23 Resolved: 03/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Query 2018-07-16 | ||||
| Participants: | |||||
| Linked BF Score: | 26 | ||||
| Description |
|
If a chunk migration fails during the setup of the sharded collection we can end up with data on only one of the two shards. If this is the case, resumeAfter is known not to work on the 3.6 branch due to |
| Comments |
| Comment by Githook User [ 03/Jul/18 ] |
|
Author: {'username': 'cswanson310', 'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com'}Message: |