hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-209) Capacity scheduler can leave application in pending state
Date Sat, 10 Nov 2012 11:17:12 GMT

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

Bikas Saha commented on YARN-209:

Attaching a fix for the issue. Also attaching a test that times out without this fix and passes
with it. There might be a simpler way to test this.
> 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
> 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

View raw message