[SERVER-30442] recipient shard should fail if donor does not return an entry for the collection in listCollections Created: 31/Jul/17 Updated: 30/Oct/23 Resolved: 02/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.10 |
| Fix Version/s: | 3.5.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2017-08-21 |
| Participants: |
| Description |
|
The recipient shard should fail if the listCollections response is empty, rather than silently continuing as it currently does. If the donor no longer has the collection, it's nonsensical for the recipient to accept a chunk for the collection from the donor. |
| Comments |
| Comment by Githook User [ 10/Aug/17 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}Message: |