[
https://issues.apache.org/jira/browse/TEZ-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Balamohan updated TEZ-1712:
----------------------------------
Attachment: TEZ-1712.2.patch
>>
What impact does not shutting down the ssl connection have in terms of
container re-use. Is there a possibility that we'll end up trying to use ssl
for subsequent DAGs which may not be configured to use it ?
>>
Good catch. In setupConnection(), check needs to be added to use of SSL
connection only when "httpConnParams.sslShuffle == true". Attached patch
addresses this.
> SSL context gets destroyed too soon after downloading data from one of the
> vertices
> -----------------------------------------------------------------------------------
>
> Key: TEZ-1712
> URL: https://issues.apache.org/jira/browse/TEZ-1712
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: TEZ-1712.1.patch, TEZ-1712.2.patch,
> tez_1712_syslog_attempt_1414454836629_0004_1_05_000001_0.txt
>
>
> In scenarios where a vertex has to download shuffle data from multiple
> sources, sslContext gets destroyed soon after data is downloaded from one of
> the vertex. This causes SSL handshake exception when data needs to be
> downloaded from other vertices and fetchers to fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
