Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1730493723.1247027294881.JavaMail.jira@brutus>
Date: Tue, 7 Jul 2009 21:28:14 -0700 (PDT)
From: "Ravi Gummadi (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-353) Allow shuffle read and connection
 timeouts to be configurable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ravi Gummadi updated MAPREDUCE-353:
-----------------------------------

    Attachment: MR-353.patch

Attaching patch that adds the config properties mapred.shuffle.connect.timeout and mapred.shuffle.read.timeout.
Please review and provide your comments.

> 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.