[SERVER-57466] Swallow connection reset-related errors received during ASIO session establishment Created: 04/Jun/21 Updated: 29/Oct/23 Resolved: 26/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.0.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shane Harvey | Assignee: | Blake Oler |
| 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: |
v5.0
|
||||||||||||||||||||||||||||
| Sprint: | Service Arch 2021-09-06, Service Arch 2021-09-20, Service Arch 2021-10-04, Service Arch 2021-11-01 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 25 | ||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||
| Description |
|
5.0.0-rc0 clusters (standalone mongod, mongos) running on macOS, I see many errors like this "ctx":"listener","msg":"Can't set socket option","attr":{"optname":"TCP_KEEPALIVE","error":"Invalid argument"}} The log is flooded with these errors:
The connections that error are coming from an otherwise idle load balancer (haproxy). When a driver connects directly to the mongod/s the error does not occur. What does this error mean and why do these errors occur for haproxy connections? The load balancer is started and stopped with this run-load-balancer.sh script, like this:
|
| Comments |
| Comment by Githook User [ 17/Mar/22 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit ffededcdc670d83f4fdf5819f5ab1d9c5750c67c)
(cherry picked from commit 37595d5ee16f06c964b9d416e5847b99c1a537d8) |
| Comment by Githook User [ 16/Mar/22 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit ffededcdc670d83f4fdf5819f5ab1d9c5750c67c)
(cherry picked from commit 37595d5ee16f06c964b9d416e5847b99c1a537d8) |
| Comment by Githook User [ 16/Oct/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 14/Oct/21 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: |
| Comment by Shane Harvey [ 01/Sep/21 ] |
|
Thanks Blake, just FYI this issue is not a blocker. The only side effect here as far as I can tell is that the server logs are flooded NETWORK errors. |
| Comment by Matthew Saltz (Inactive) [ 16/Jun/21 ] |
|
Okay, thanks! |
| Comment by Jeffrey Yemin [ 15/Jun/21 ] |
|
That's correct, shane.harvey |
| Comment by Matthew Saltz (Inactive) [ 15/Jun/21 ] |
|
shane.harvey Would we need to fix this before 5.0 release? |