[
https://issues.apache.org/jira/browse/MAPREDUCE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729536#action_12729536
]
Jothi Padmanabhan commented on MAPREDUCE-353:
---------------------------------------------
Some minor changes:
# Add a comment in the xml file saying that these should be treated as cluster
level configuration parameters
# Add the "Expert" tag to the description in the xml
> 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
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Attachments: MR-353.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.