hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-209) Capacity scheduler can leave application in pending state
Date Wed, 28 Nov 2012 17:02:59 GMT

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

Hadoop QA commented on YARN-209:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12552973/YARN-209.1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/176//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/176//console

This message is automatically generated.
                
> Capacity scheduler can leave application in pending state
> ---------------------------------------------------------
>
>                 Key: YARN-209
>                 URL: https://issues.apache.org/jira/browse/YARN-209
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>             Fix For: 3.0.0
>
>         Attachments: YARN-209.1.patch, YARN-209-test.patch
>
>
> Say application A is submitted but at that time it does not meet the bar for activation
because of resource limit settings for applications. After that if more hardware is added
to the system and the application becomes valid it still remains in pending state, likely
forever.
> This might be rare to hit in real life because enough NM's heartbeat to the RM before
applications can get submitted. But a change in settings or heartbeat interval might make
it easier to repro. In RM restart scenarios, this will likely hit more if its implemented
by re-playing events and re-submitting applications to the scheduler before the RPC to NM's
is activated.

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