[SERVER-31680] ReplSetMonitor::getHostOrRefresh times out too quickly Created: 23/Oct/17 Updated: 12/Aug/19 Resolved: 12/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
The max time default for ReplSetMonitor::getHostOrRefresh is clearly too low at 15 seconds, given failover in our testing can easily take that long on a slow machine or just timing election runs just right.
However, ReplSetMonitor::getHostOrRefresh timed out after 20 seconds in the linked BF, so this suggests a caller is passing in 20 seconds, which again is too short to be reasonable for testing. |
| Comments |
| Comment by Benjamin Caimano (Inactive) [ 12/Aug/19 ] |
|
I think the 15s timeout is fine for normal use. It's not like customers would want to be waiting around longer than that unless they've set their maxTimeMS. Since this isn't blowing up our CI anymore, I'm closing this as "Won't Fix". |