[SERVER-50306] ReplicaSetMonitor::getHostsOrRefresh does not respect wait time in socket connect Created: 13/Aug/20 Updated: 27/Oct/23 Resolved: 14/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Sharding |
| Affects Version/s: | 4.0.19 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
This socket timeout is a constant of 5 seconds. It should instead respect the maxWait parameter on getHostOrRefresh when the call to refreshUntilMatches is made. Otherwise this could lead to not respecting a user's MaxTimeMS if the MaxTimeMS is less than 5 seconds. |
| Comments |
| Comment by Matthew Saltz (Inactive) [ 14/Aug/20 ] |
|
I realized this was based on a misunderstanding of how the RSM worked in 4.0. getHostsOrRefresh actually joins existing refreshes, and so won't cause additional blocking for clients calling getHostsOrRefresh |