[
https://issues.apache.org/jira/browse/KUDU-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3352:
--------------------------------
Status: In Review (was: Open)
> 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.13.0, 1.14.0, 1.15.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
>
> 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)
