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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/02/27 20:51:05 UTC

[jira] [Created] (YARN-3277) Queue's current-max-limit should be updated before allocate reserved container.

Wangda Tan created YARN-3277:
--------------------------------

             Summary: Queue's current-max-limit should be updated before allocate reserved container.
                 Key: YARN-3277
                 URL: https://issues.apache.org/jira/browse/YARN-3277
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: capacityscheduler, resourcemanager
            Reporter: Wangda Tan
            Assignee: Wangda Tan


This is introduced by changes of YARN-3265. With YARN-2008, when RM allocates reserved container, it goes to LeafQueue directly, then goes up to root to get LeafQueue's current-max-limit correct. Now we will not go up, so LeafQueue cannot get maxQueueLimit updated before allocating reserved container.

One possible solution is, we can still start from root when allocate reserved container, but goes to LeafQueue which reserved container belongs to from top to bottom.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)