[jira] [Resolved] (KUDU-1963) Java client logs NPE if a connection is closed by client during negotiation

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon resolved KUDU-1963.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0
                   1.3.1

fixed in ac6e24fc2299430b5f70146324bef2d2e8a4b8bc (1.4) and ae25d1c1fb8d00b8886711291235d0db1f161d33 (1.3.1)

> Java client logs NPE if a connection is closed by client during negotiation
> ---------------------------------------------------------------------------
>
>                 Key: KUDU-1963
>                 URL: https://issues.apache.org/jira/browse/KUDU-1963
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.3.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 1.3.1, 1.4.0
>
>
> This is noted in KUDU-1894 but I don't know if it's the root cause of the ITClient flakiness, so I'm opening a new JIRA for this:
> If the client is closed (or a connection to a TS is closed) while it's in the progress of negotiating, it will result in an error stating "javax.net.ssl.SSLException: renegotiation attempted by peer; closing the connection" followed by an NPE in sendQueuedRpcs().
> This is being triggered by Impala in a stress workload with a high query rate.



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