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 "Arun C Murthy (JIRA)" <ji...@apache.org> on 2014/03/20 19:42:52 UTC

[jira] [Commented] (YARN-1051) YARN Admission Control/Planner: enhancing the resource allocation model with time.

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

Arun C Murthy commented on YARN-1051:
-------------------------------------

Thanks [~subru], I'll take a look at the update.

One thing I've mentioned to [~curino] offline is that I think we are better of relying on enhancing/reducing *priorities* for applications to effect reservations rather than relying on adding/removing queues.

Priorities within the same queue is an often requested feature anyway - that way we can solve multiple goals (operational-feature/reservations) with the same underlying mechanism i.e. priorities.

> 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
>         Attachments: YARN-1051-design.pdf, curino_MSR-TR-2013-108.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
(v6.2#6252)