You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/08/07 07:36:45 UTC

[jira] [Updated] (YARN-4026) FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests

     [ https://issues.apache.org/jira/browse/YARN-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wangda Tan updated YARN-4026:
-----------------------------
    Summary: FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests  (was: FiCaSchedulerApp: Revisit ContainerAllocator interface design)

> FiCaSchedulerApp: ContainerAllocator should be able to choose how to order pending resource requests
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4026
>                 URL: https://issues.apache.org/jira/browse/YARN-4026
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>
> After YARN-3983, we have an extensible ContainerAllocator which can be used by FiCaSchedulerApp to decide how to allocate resources.
> While working on YARN-1651 (allocate resource to increase container), I found one thing in existing logic not flexible enough:
> - ContainerAllocator decides what to allocate for a given node and priority: To support different kinds of resource allocation, for example, priority as weight / skip priority or not, etc. It's better to let ContainerAllocator to choose how to order resource request according to priorities.



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