[
https://issues.apache.org/jira/browse/YARN-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787680#comment-13787680
]
Bikas Saha commented on YARN-1278:
----------------------------------
(Keyboard messed up)
Even restart shouldn't delete existing resources since thats an expensive loss.
We should be able to reconstruct the cache state from the previously downloaded
files. However, thats probably a big change.
For the purposes of this jira NM should delete resources on resync.
> New AM does not start after rm restart
> --------------------------------------
>
> Key: YARN-1278
> URL: https://issues.apache.org/jira/browse/YARN-1278
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.1-beta
> Reporter: Yesha Vora
> Assignee: Hitesh Shah
> Priority: Blocker
> Attachments: YARN-1278.1.patch
>
>
> The new AM fails to start after RM restarts. It fails to start new
> Application master and job fails with below error.
> /usr/bin/mapred job -status job_1380985373054_0001
> 13/10/05 15:04:04 INFO client.RMProxy: Connecting to ResourceManager at
> hostname
> Job: job_1380985373054_0001
> Job File: /user/abc/.staging/job_1380985373054_0001/job.xml
> Job Tracking URL :
> http://hostname:8088/cluster/app/application_1380985373054_0001
> Uber job : false
> Number of maps: 0
> Number of reduces: 0
> map() completion: 0.0
> reduce() completion: 0.0
> Job state: FAILED
> retired: false
> reason for failure: There are no failed tasks for the job. Job is failed due
> to some other reason and reason can be found in the logs.
> Counters: 0
--
This message was sent by Atlassian JIRA
(v6.1#6144)
