hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5062) MR AM should read max-retries information from the RM
Date Mon, 25 Mar 2013 22:33:15 GMT

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

Vinod Kumar Vavilapalli updated MAPREDUCE-5062:
-----------------------------------------------

    Attachment: MAPREDUCE-5062-20130325.1.txt

Reverting the retry number to 1 as YARN-378 set that to 1 on RM side. I think we should change
that, perhaps in a separate ticket.

I'm checking this in to unblock builds.
                
> MR AM should read max-retries information from the RM
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-5062
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5062
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Zhijie Shen
>         Attachments: MAPREDUCE-5062.1.patch, MAPREDUCE-5062-20130325.1.txt, MAPREDUCE-5062-20130325.txt,
MAPREDUCE-5062.2.patch
>
>
> Change MR AM to use app-retry maximum limit that is made available by RM after YARN-378.

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