hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlo Curino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1051) YARN Admission Control/Planner: enhancing the resource allocation model with time.
Date Thu, 17 Dec 2015 20:05:46 GMT

    [ https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062692#comment-15062692

Carlo Curino commented on YARN-1051:

[~lars_francke], you can refer to the general tech-report for more of the top-level ideas/design.
As for how-to-use documentation, you are right it is long overdue. A couple of follow up umbrella
JIRAs YARN-2573 (HA for the reservation system), and YARN-2572 (various improvements/extensions
and REST API work) can give you some more context of what is brewing. But, in particular,
as part of the umbrella JIRA YARN-2572, I have just opened YARN-4468 that is intended to provide
general documentation of the reservaiton system and its (recently added) REST api. We will
try to get to it soon.  

> YARN Admission Control/Planner: enhancing the resource allocation model with time.
> ----------------------------------------------------------------------------------
>                 Key: YARN-1051
>                 URL: https://issues.apache.org/jira/browse/YARN-1051
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler, resourcemanager, scheduler
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>             Fix For: 2.6.0
>         Attachments: YARN-1051-design.pdf, YARN-1051.1.patch, YARN-1051.patch, curino_MSR-TR-2013-108.pdf,
socc14-paper15.pdf, techreport.pdf
> In this umbrella JIRA we propose to extend the YARN RM to handle time explicitly, allowing
users to "reserve" capacity over time. This is an important step towards SLAs, long-running
services, workflows, and helps for gang scheduling.

This message was sent by Atlassian JIRA

View raw message