[ https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140910#comment-15140910 ]
Lei Guo commented on YARN-1051: ------------------------------- [~curino], for enterprise customer, the scheduling policy will be complicate. How this planner to satisfy complex scheduling policy other than FIFO? As [~acmurthy] asked earlier, the priority based scheduling is one basic case on scheduling policy, what's the best practice for this? > 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 (v6.3.4#6332)