hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1090) Job does not get into Pending State
Date Fri, 30 Aug 2013 22:45:52 GMT

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

Sandy Ryza commented on YARN-1090:
----------------------------------

My understanding was that an application is "Pending" if no AM has yet been allocated to it.
 Can you go a little more into what the issue is with this definition?

Also, whatever we decide, is there somewhere where we can document exactly what these mean?
                
> Job does not get into Pending State
> -----------------------------------
>
>                 Key: YARN-1090
>                 URL: https://issues.apache.org/jira/browse/YARN-1090
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: yeshavora
>            Assignee: Jian He
>         Attachments: YARN-1090.patch
>
>
> When there is no resource available to run a job, next job should go in pending state.
RM UI should show next job as pending app and the counter for the pending app should be incremented.
> But Currently. Next job stays in ACCEPTED state and No AM has been assigned to this job.Though
Pending App count is not incremented. 
> Running 'job status <nextjob>' shows job state=PREP. 
> $ mapred job -status job_1377122233385_0002
> 13/08/21 21:59:23 INFO client.RMProxy: Connecting to ResourceManager at host1/ip1
> Job: job_1377122233385_0002
> Job File: /ABC/.staging/job_1377122233385_0002/job.xml
> Job Tracking URL : http://host1:port1/application_1377122233385_0002/
> Uber job : false
> Number of maps: 0
> Number of reduces: 0
> map() completion: 0.0
> reduce() completion: 0.0
> Job state: PREP
> retired: false
> reason for failure:

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