You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2012/11/10 11:25:13 UTC

[jira] [Created] (YARN-209) Capacity scheduler can leave application in pending state

Bikas Saha created YARN-209:
-------------------------------

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


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