[SERVER-53520] Verify resharding doesn't result in recipient shards copying documents they don't own Created: 24/Dec/20 Updated: 29/Oct/23 Resolved: 05/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-fuzzer | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-02-08 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
This would be added to the ReshardingTest fixture. Max's thought is to use DataConsistencyChecker.getDiff() to assert there is an empty diff between the contents of the temporary resharding collection with read concern levels "local" and "available". |
| Comments |
| Comment by Githook User [ 05/Feb/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |