[SERVER-68329] Avoid dropping pools for any error thrown during connection setup Created: 26/Jul/22 Updated: 29/Oct/23 Resolved: 28/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0, 6.0.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Alex Li |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||||||
| Sprint: | Service Arch 2022-09-05, Service Arch 2022-09-19, Service Arch 2022-10-03 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We currently convert all errors encountered during connection-setup to HostUnreachable, which causes the connection-pool to tag the target host as unhealthy and drop all connections (see below for more details). This behavior is not correct for all errors (e.g., EINPROGRESS) and the error-handling code should be adjusted accordingly. A possible solution is to only drop connections for a specific group of errors that are a clear indication that the target host is unhealthy. Here is the path through which we convert all connection setup errors to HostUnreachable:
|
| Comments |
| Comment by Githook User [ 14/Jun/23 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |
| Comment by Githook User [ 27/Sep/22 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: |