[SERVER-25050] Re-evaluate 30 second maxTimeMs included with every command sent to the config servers Created: 13/Jul/16 Updated: 13/Aug/16 Resolved: 30/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.9 |
| Fix Version/s: | 3.3.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 18 (08/05/16) | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Mongos currently adds a 30 second timeout to all commands it sends to the config servers. In 3.4, however, we are running a lot more on config servers, and some of the commands we run can be performing multiple network and disk i/o operations, so it can sometimes be reasonable for them to take longer than 30 seconds to complete. We are already seeing sporadic failures in evergreen related to _configsvrAddShard timing out occasionally |
| Comments |
| Comment by Githook User [ 30/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change makes mongos commands to retrieve the maxTimeMS from the |
| Comment by Githook User [ 30/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: No functional changes, just cleanup the Strategy class and rename |