hadoop-yarn-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] (YARN-1278) New AM does not start after rm restart
Date Sun, 06 Oct 2013 17:30:42 GMT

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

Vinod Kumar Vavilapalli updated YARN-1278:
------------------------------------------

    Attachment: YARN-1278.2.patch

Same patch but
 - removes the switches on cleanup-containers and cleanup-apps
 - adds a code comment and
 - cleans up the test to explicitly validate the existence of the app.

The test in the previous patch failed without the main code changes and passed with. So we
are good.

Will check this in if Jenkins says okay too.

> 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, YARN-1278.2.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)

Mime
View raw message