hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-6164) "mapreduce.reduce.shuffle.fetch.retry.timeout-ms" should be set to 3 minutes instead of 30 seconds by default to keep insistent with other retry timeout
Date Mon, 17 Nov 2014 12:24:33 GMT
Junping Du created MAPREDUCE-6164:
-------------------------------------

             Summary: "mapreduce.reduce.shuffle.fetch.retry.timeout-ms" should be set to 3
minutes instead of 30 seconds by default to keep insistent with other retry timeout 
                 Key: MAPREDUCE-6164
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6164
             Project: Hadoop Map/Reduce
          Issue Type: Bug
            Reporter: Junping Du
            Assignee: Junping Du


In MAPREDUCE-5891, we are adding retry logic to MAPREDUCE shuffle stage for fetcher can be
survival during NM downtime (with shuffle service down as well). In many places, we are setting
the default timeout to be 3 minutes (connection timeout, etc.) to tolerant possible more time
for NM down, but we are making "mapreduce.reduce.shuffle.fetch.retry.timeout-ms" to be 30
seconds which is not consistent here. We should change this to 180 seconds. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message