You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/07/16 16:04:49 UTC
[jira] [Commented] (MAPREDUCE-5396) Application is "FAILED" when
multiple appmaster attempts are spawned
[ https://issues.apache.org/jira/browse/MAPREDUCE-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709791#comment-13709791 ]
Jason Lowe commented on MAPREDUCE-5396:
---------------------------------------
Moved this to MAPREDUCE since this is an issue with the MRAppMaster. Unless the app attempt is the last one, the MR AM should not be deleting the staging directory when told to shutdown by a heartbeat response from the RM.
> Application is "FAILED" when multiple appmaster attempts are spawned
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-5396
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5396
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 2.0.5-alpha
> Reporter: Nishan Shetty
> Assignee: Devaraj K
>
> 1.Run job with 142 maps
> 2.After some map tasks executed kill NM where appmaster running(Using kill -9 cmd)
> 3.Now obeserve that till NM expiry interval that appmaster will be running after NM expiry interval that appmaster will be killed and new appmaster will be launched
> Observations:
> -------------------
> 1.First appmaster while going down deletes the staging dir of job
> 2.While new appmaster is running it will kill all the tasks running in it and fails the application saying files in staging dir not present
--
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