[SERVER-12947] Dont use MultipleErrorsOccurred path if all errors are the same Created: 27/Feb/14 Updated: 30/Jan/19 Resolved: 30/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Usability, Write Ops |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 4.1.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Janna Golden |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2019-02-11 | ||||
| Participants: | |||||
| Description |
|
It would be better to just return the common error
|
| Comments |
| Comment by Githook User [ 30/Jan/19 ] |
|
Author: {'email': 'golden.janna@gmail.com', 'name': 'jannaerin'}Message: |
| Comment by Kaloian Manassiev [ 24/Jan/19 ] |
|
janna.golden, I am not sure what the "MultipleErrorsOccurred" path isĀ and this might as well be something that we got rid of, but can you please check with redbeard0531 and verify whether this is gone away, now that you are working in the write commands code. |
| Comment by Daniel Pasette (Inactive) [ 03/Mar/14 ] |
|
I think the duplication is fine, but I would like to see the source of the error. That is, show the shard or host which produced the error. |