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] [Created] (MAPREDUCE-5956) MapReduce AM should not
Date Wed, 02 Jul 2014 03:00:30 GMT
Vinod Kumar Vavilapalli created MAPREDUCE-5956:
--------------------------------------------------

             Summary: MapReduce AM should not 
                 Key: MAPREDUCE-5956
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5956
             Project: Hadoop Map/Reduce
          Issue Type: Sub-task
            Reporter: Vinod Kumar Vavilapalli
            Assignee: Vinod Kumar Vavilapalli
            Priority: Blocker


Found this while reviewing YARN-2074. The problem is that after YARN-2074, we don't count
AM preemption towards AM failures on RM side, but MapReduce AM itself checks the attempt id
against the max-attempt count to determine if this is the last attempt.
{code}
    public void computeIsLastAMRetry() {
      isLastAMRetry = appAttemptID.getAttemptId() >= maxAppAttempts;
    }
{code}
This causes issues w.r.t deletion of staging directory etc..



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message