[SERVER-40396] Remove invalid check from sharded moveChunk concurrency workload Created: 01/Apr/19 Updated: 29/Oct/23 Resolved: 08/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2019-04-22 | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
This check is not valid because it's possible that even if a chunk migration failed from shard A to shard B, it's possible that shard B still has orphaned documents from that chunk from when it previously moved from shard B to shard A. |
| Comments |
| Comment by Githook User [ 08/Apr/19 ] |
|
Author: {'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz', 'username': 'saltzm'}Message: |