hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4902) [Umbrella] Generalized and unified scheduling-strategies in YARN
Date Thu, 31 Mar 2016 00:51:25 GMT

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

Vinod Kumar Vavilapalli updated YARN-4902:
------------------------------------------
    Attachment: Generalized and unified scheduling-strategies in YARN -v0.pdf

Attaching a design that [~leftnoteasy] and I have been working on offline with inputs from
[~jianhe] and [~vvasudev].

This document is our initial take on generalizing scheduling strategies in YARN so that we
not only simplify our existing API model and streamline our implementation, but also make
it extensible enough to accommodate any future scheduling-functionality.

We created this document mainly to coalesce thoughts similar to ours that we heard during
interactions in the community over a long period of time. We hope to trigger a conversation
towards a design with more comprehensive details as needed and lesser gaps in it.

Feedback appreciated!

> [Umbrella] Generalized and unified scheduling-strategies in YARN
> ----------------------------------------------------------------
>
>                 Key: YARN-4902
>                 URL: https://issues.apache.org/jira/browse/YARN-4902
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Wangda Tan
>         Attachments: Generalized and unified scheduling-strategies in YARN -v0.pdf
>
>
> Apache Hadoop YARN's ResourceRequest mechanism is the core part of the YARN's scheduling
API for applications to use. The ResourceRequest mechanism is a powerful API for applications
(specifically ApplicationMasters) to indicate to YARN what size of containers are needed,
and where in the cluster etc.
> However a host of new feature requirements are making the API increasingly more and more
complex and difficult to understand by users and making it very complicated to implement within
the code-base.
> This JIRA aims to generalize and unify all such scheduling-strategies in YARN.



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

Mime
View raw message