You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/05/18 01:14:04 UTC

[jira] [Resolved] (KUDU-1894) ITClient very flaky since introduction of TLS

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

Todd Lipcon resolved KUDU-1894.
-------------------------------
          Resolution: Cannot Reproduce
       Fix Version/s: n/a
    Target Version/s:   (was: 1.4.0)

I haven't seen this again in the last month

> ITClient very flaky since introduction of TLS
> ---------------------------------------------
>
>                 Key: KUDU-1894
>                 URL: https://issues.apache.org/jira/browse/KUDU-1894
>             Project: Kudu
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.3.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: n/a
>
>
> Since introducing TLS support in the Java client, ITClient seems to hang/timeout quite often. It always spews some error about TLS renegotiation, but it seems like that error description is incorrect -- really it seems more likely that something is amiss with the way this test tries to shut down client connections by reaching into the Netty channel.
> Either way we should investigate for 1.3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)