[
https://issues.apache.org/jira/browse/TEZ-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879994#comment-15879994
]
Rajesh Balamohan commented on TEZ-3633:
---------------------------------------
I was able to reproduce the issue. Issue seems to be due to the change
introduced in https://issues.apache.org/jira/browse/MAPREDUCE-6474 which closes
the channel.
Keep-Alive and timeout values are mentioned correctly in the headers.
However, due to MAPREDUCE-6474 change, it ends up closing the connection at
server side. This breaks keep-alive and internally HttpUrlConnection fixes
things up. [~jeagles], should this be fixed in mapreduce shuffle handler as
well?
> Implement keep-alive timeout in tez shuffle handler
> ---------------------------------------------------
>
> Key: TEZ-3633
> URL: https://issues.apache.org/jira/browse/TEZ-3633
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-3633.1.patch
>
>
> MAPREDUCE-5787 which added keep-alive to mapreduce shuffle handler was not
> fully functional as despite advertising keep-alive option and adding the
> header to the response, all connections were closed immediately after write.
> This reduced the performance of certain fetches as now time is spent
> requesting a second get to the same serve, only for that server to reset the
> connection forcing the client to reestablish the connection on another port.
> The details of this is hidden behind HttpURLConnection and doesn't show in
> any log file at default logging level. However TCP sniffing does show errant
> behavior.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
