[
https://issues.apache.org/jira/browse/YARN-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542755#comment-14542755
]
Karthik Kambatla commented on YARN-3306:
----------------------------------------
The branch is not only to avoid interfering with other work, but also to ensure
we don't ship bits we don't have to. Integration points being narrow is
probably more a reason to work on a branch.
> [Umbrella] Proposing per-queue Policy driven scheduling in YARN
> ---------------------------------------------------------------
>
> Key: YARN-3306
> URL: https://issues.apache.org/jira/browse/YARN-3306
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Attachments: PerQueuePolicydrivenschedulinginYARN.pdf
>
>
> Scheduling layout in Apache Hadoop YARN today is very coarse grained. This
> proposal aims at converting today’s rigid scheduling in YARN to a per-queue
> policy driven architecture.
> We propose the creation of a common policy framework and implement acommon
> set of policies that administrators can pick and chose per queue
> - Make scheduling policies configurable per queue
> - Initially, we limit ourselves to a new type of scheduling policy that
> determines the ordering of applications within the leaf queue
> - In the near future, we will also pursue parent queue level policies and
> potential algorithm reuse through a separate type of policies that control
> resource limits per queue, user, application etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)