You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2018/12/23 03:54:00 UTC

[jira] [Resolved] (KUDU-2647) client connection to *:7051 recv error: Network error: failed to read from TLS socket: Connection reset by peer (error 104)

     [ https://issues.apache.org/jira/browse/KUDU-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Berkeley resolved KUDU-2647.
---------------------------------
       Resolution: Information Provided
    Fix Version/s: n/a

By default, Kudu will encrypt communications between clients and servers and among servers using TLS, so an error like this can happen even if you did not configure any TLS connections.

In the future, questions like this are best asked on the user@kudu.apache.org mailing list or in the public [Kudu Slack|https://getkudu-slack.herokuapp.com/].

> client connection to *:7051 recv error: Network error: failed to read from TLS socket: Connection reset by peer (error 104)
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KUDU-2647
>                 URL: https://issues.apache.org/jira/browse/KUDU-2647
>             Project: Kudu
>          Issue Type: Bug
>            Reporter: qinzl_1
>            Priority: Major
>             Fix For: n/a
>
>
> i did not open any TLS/SSL config.why have this error



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)