[SERVER-25999] Mongos applies errors received from config server as config server errors, rather than a shard the config server calls and returns the error from Created: 07/Sep/16 Updated: 06/Mar/20 Resolved: 01/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Sharding 2016-10-10, Sharding 2016-10-31, Sharding 2016-11-21 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
ShardRemote::updateReplSetMonitor marks a host as not master on InterruptedDueToReplStateChange errors. However, a mongos can send a command to the config, which then sends to a shard, and the shard returns the error, but the mongos marks the config server as not master. This is generally true of all errors that are interpreted as the first contacted server's fault, not any subsequent servers that are called down the line. This is an issue for existing config commands that forward commands to the shards and return that result (like the balancer!) |
| Comments |
| Comment by Githook User [ 28/Oct/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |
| Comment by Esha Maharishi (Inactive) [ 06/Oct/16 ] |
|
addShard does this in at least one place: |