[ 
https://issues.apache.org/jira/browse/TEZ-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880617#comment-15880617
 ] 

Jonathan Eagles commented on TEZ-3633:
--------------------------------------

[~rajesh.balamohan], I will go ahead and file a MapReduce jira and port the 
patch 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, with_hadoop_2.7.3.png
>
>
> 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)

Reply via email to