[SERVER-23784] Don't use 30 second network timeout on commands sent to shards through the ShardRegistry Created: 18/Apr/16 Updated: 25/Jan/17 Resolved: 18/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.6, 3.3.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||||||
| Sprint: | Sharding 13 (04/22/16) | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
In 3.2 we run many commands through the ShardRegistry, instead of using DBClient directly. We wanted to always use a 30 second timeout for all commands sent to the config servers through the ShardRegistry, but in doing so we accidentally started using the 30 second timeout for commands run against shards as well, where it may not be right to do so. |
| Comments |
| Comment by Githook User [ 18/Apr/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit a42a3d9e45f23e979f20113549ad91a6886ede3d) |
| Comment by Githook User [ 18/Apr/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |