[SERVER-25938] ShardLocal::runCommand variants should parse writeConcernError even when the command failed Created: 01/Sep/16 Updated: 25/Jan/17 Resolved: 02/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | 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 2016-09-19 |
| Participants: |
| Description |
|
It is completely valid for commands to both fail and also have a write concern error. ShardRemote already handles this correctly, ShardLocal needs to be updated to behave the same as ShardRemote. This leads to the following weird error appearing on config servers:
|
| Comments |
| Comment by Githook User [ 02/Sep/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |