hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MAPREDUCE-4604) In mapred-default, mapreduce.map.maxattempts & mapreduce.reduce.maxattempts defaults are set to 4 as well as mapreduce.job.maxtaskfailures.per.tracker.
Date Thu, 11 Oct 2012 17:50:06 GMT

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

Arun C Murthy closed MAPREDUCE-4604.
------------------------------------

    
> In mapred-default, mapreduce.map.maxattempts & mapreduce.reduce.maxattempts defaults
are set to 4 as well as mapreduce.job.maxtaskfailures.per.tracker. 
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4604
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4604
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3, 2.0.0-alpha, trunk
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>            Priority: Critical
>             Fix For: 0.23.3, 2.0.2-alpha
>
>         Attachments: MAPREDUCE-4604.patch, MAPREDUCE-4604.patch
>
>
> This causes the AM to fail the job at the same time as it blacklists a node, thus never
actually trying another node.
> Marking as critical because we need this in 0.23.3 before it releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message