[SERVER-16820] Use socket timeout in additional places Created: 13/Jan/15 Updated: 06/Dec/22 Resolved: 16/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
There are various places which don't set a socket timeout and use the default of 0 (from the constructor/etc). These places should be updated to use a non-zero socket timeout (most code uses 10/30 seconds for example). The following should be changed: |
| Comments |
| Comment by Mira Carey [ 16/Feb/18 ] |
|
In my mind, we should be solving problems like this with maxtime ms, rather than figuring out the right socket timeouts to plumb. If we don't have a notion of a high level timeout for these ops, it's not clear to me if a networking timeout should even be a failure |