You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2022/02/11 04:56:00 UTC
[jira] [Created] (KUDU-3352) Malfunction in Sockaddr::HashCode() could lead to running out of connections in a busy Kudu cluster
Alexey Serbin created KUDU-3352:
-----------------------------------
Summary: Malfunction in Sockaddr::HashCode() could lead to running out of connections in a busy Kudu cluster
Key: KUDU-3352
URL: https://issues.apache.org/jira/browse/KUDU-3352
Project: Kudu
Issue Type: Bug
Components: client, master, tserver
Affects Versions: 1.15.0, 1.14.0, 1.13.0
Reporter: Alexey Serbin
Assignee: Alexey Serbin
Since the {{Sockaddr}} class has been updated to handle various address families, an issue with uninitialized memory in the {{storage_.in.sin_zero}} started affecting the behavior of the {{Sockaddr::HashCode()}} method.
As the result, {{ReactorThread::FindOrStartConnection()}} would create a new connection to the specified remote even if a connection with the required credentials policy had already been established. In a very busy Kudu cluster that could lead to running out of connections, where an attempt to establish a new connection would fail with {{EADDRNOTAVAIL}} error (Cannot assign requested address).
Credit goes to [~wzhou] for detecting and troubleshooting the issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)