impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailesh Mukil (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-5182) Explicitly close connection to impalad on error from shell
Date Fri, 21 Apr 2017 00:43:04 GMT

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

Sailesh Mukil resolved IMPALA-5182.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.9.0

https://github.com/apache/incubator-impala/commit/2a34076b2db99bb83eb3e3929d310fcb10b1dd44

> Explicitly close connection to impalad on error from shell
> ----------------------------------------------------------
>
>                 Key: IMPALA-5182
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5182
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>            Reporter: Sailesh Mukil
>            Assignee: Sailesh Mukil
>              Labels: security, shell
>             Fix For: Impala 2.9.0
>
>
> When using connections secured with SSL, a connection close comprises a bi-directional
SSL_shutdown(). The second part of the bi-directional shutdown requires that the client also
close the socket explicitly, and the server blocks till it gets the close notification from
the client.
> We need to make sure that the impala-shell does the explicit close on an error.



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

Mime
View raw message