hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1090) Job does not get into Pending State
Date Sat, 05 Oct 2013 22:37:43 GMT

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

Hudson commented on YARN-1090:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #4549 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4549/])
YARN-1090. Fixed CS UI to better reflect applications as non-schedulable and not as pending.
Contributed by Jian He. (acmurthy: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1529538)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/QueueMetrics.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/CapacitySchedulerPage.java


> 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: Yesha Vora
>            Assignee: Jian He
>             Fix For: 2.1.2-beta
>
>         Attachments: YARN-1090.1.patch, YARN-1090.2.patch, YARN-1090.3.patch, 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message