Chris Douglas commented on YARN-3806:

[~wshao] Please don't delete obsoleted versions of the design doc, as it 
orphans discussion about them. Also, as you're making updates, please note the 
changes so people don't have to diff the docs.

> Proposal of Generic Scheduling Framework for YARN
> -------------------------------------------------
>                 Key: YARN-3806
>                 URL: https://issues.apache.org/jira/browse/YARN-3806
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>            Reporter: Wei Shao
>         Attachments: ProposalOfGenericSchedulingFrameworkForYARN-V1.05.pdf, 
> ProposalOfGenericSchedulingFrameworkForYARN-V1.06.pdf
> Currently, a typical YARN cluster runs many different kinds of applications: 
> production applications, ad hoc user applications, long running services and 
> so on. Different YARN scheduling policies may be suitable for different 
> applications. For example, capacity scheduling can manage production 
> applications well since application can get guaranteed resource share, fair 
> scheduling can manage ad hoc user applications well since it can enforce 
> fairness among users. However, current YARN scheduling framework doesn’t have 
> a mechanism for multiple scheduling policies work hierarchically in one 
> cluster.
> YARN-3306 talked about many issues of today’s YARN scheduling framework, and 
> proposed a per-queue policy driven framework. In detail, it supported 
> different scheduling policies for leaf queues. However, support of different 
> scheduling policies for upper level queues is not seriously considered yet. 
> A generic scheduling framework is proposed here to address these limitations. 
> It supports different policies (fair, capacity, fifo and so on) for any queue 
> consistently. The proposal tries to solve many other issues in current YARN 
> scheduling framework as well.
> Two new proposed scheduling policies YARN-3807 & YARN-3808 are based on 
> generic scheduling framework brought up in this proposal.

This message was sent by Atlassian JIRA

Reply via email to