hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-454) FS could wait until next NODE_UPDATE event to schedule a reserved container
Date Thu, 07 Mar 2013 03:18:12 GMT
Karthik Kambatla created YARN-454:
-------------------------------------

             Summary: FS could wait until next NODE_UPDATE event to schedule a reserved container
                 Key: YARN-454
                 URL: https://issues.apache.org/jira/browse/YARN-454
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: scheduler
    Affects Versions: 2.0.3-alpha
            Reporter: Karthik Kambatla
            Assignee: Karthik Kambatla


FS#nodeUpdate() allocates reserved containers first. However, it seems (from code observation):
if an app reserves a container on a node while FS is scheduling a task on that node from the
non-reserved pool, the request is skipped in that NODE_UPDATE event. It is addressed on the
next event.

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