[SERVER-23782] make Shard::_runCommand and Shard::_exhaustiveFindOnConfig take a timeout argument Created: 18/Apr/16 Updated: 06/Dec/22 Resolved: 21/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.4 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, kConfigCommandTimeout (30 seconds) is always used. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 18/Apr/16 ] |
|
Hmm... I wonder if this could be related to |