[SERVER-26857] Handle multiple server error propagation in addShard Created: 01/Nov/16 Updated: 03/Nov/16 Resolved: 03/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 2016-11-21 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Code that should be using the new Shard::shouldErrorBePropagated function: https://github.com/mongodb/mongo/blob/r3.3.15/src/mongo/s/catalog/sharding_catalog_manager_impl.cpp#L493-L499. Should double check the rest of addShard, as well, for improper error propagation. |