[
https://issues.apache.org/jira/browse/MAPREDUCE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732607#action_12732607
]
Hudson commented on MAPREDUCE-353:
----------------------------------
Integrated in Hadoop-Mapreduce-trunk #25 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/25/])
> Allow shuffle read and connection timeouts to be configurable
> -------------------------------------------------------------
>
> Key: MAPREDUCE-353
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-353
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.21.0
> Reporter: Arun C Murthy
> Assignee: Ravi Gummadi
> Fix For: 0.21.0
>
> Attachments: MR-353.patch, MR-353.v1.patch
>
>
> It would be good for latency-sensitive applications to tune the shuffle
> read/connection timeouts... in fact this made a huge difference to terasort
> since we were seeing individual shuffles stuck for upwards of 60s and had to
> have a very small read timeout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
