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

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.3.1, 1.4.0
• Component/s: client
• Target Version/s: 1.3.1, 1.4.0
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 30/Mar/17 23:03
• Updated: 04/Apr/17 21:45
• Resolved: 04/Apr/17 21:45

Description

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.

Issue Links

• relates to: KUDU-1894 ITClient very flaky since introduction of TLS