hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5127) MR job succeeds and exits even when unregister with RM fails
Date Tue, 16 Apr 2013 22:45:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633508#comment-13633508
] 

Jian He commented on MAPREDUCE-5127:
------------------------------------

Another scenario regarding AM unregister failing: when RM is restarted beyond maxAttempLimit,
after YARN-534, it will remove application state and not populate the attempts back. This
will lead AM unregister to fail 
                
> MR job succeeds and exits even when unregister with RM fails
> ------------------------------------------------------------
>
>                 Key: MAPREDUCE-5127
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5127
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster, resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>
> MR app master will clean staging dir, if the job is already succeeded and asked to reboot.
If the finishApplicationMaster call fails, RM will consider this job unfinished and launch
further attempts, further attempts will fail because staging dir is cleaned

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