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

Carlo Curino commented on YARN-3656:
------------------------------------

+1 on this patch. I committed this to trunk/branch-2, after manually inspecting 
the checkstyle and javadoc (fix a couple more but the rest will not go away as 
checkstyle misses a few uses of link tag in javadoc). 

Thanks [~jyaniv] and [~imenache] for this important contribution, (and for 
having tested it and polished those algos endlessly). 
Thanks to [~subru] for helping sheparding this and [~asuresh] for reviewing. 

> LowCost: A Cost-Based Placement Agent for YARN Reservations
> -----------------------------------------------------------
>
>                 Key: YARN-3656
>                 URL: https://issues.apache.org/jira/browse/YARN-3656
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler, resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Ishai Menache
>            Assignee: Jonathan Yaniv
>              Labels: capacity-scheduler, resourcemanager
>             Fix For: 2.8.0
>
>         Attachments: LowCostRayonExternal.pdf, YARN-3656-v1.1.patch, 
> YARN-3656-v1.2.patch, YARN-3656-v1.3.patch, YARN-3656-v1.4.patch, 
> YARN-3656-v1.5.patch, YARN-3656-v1.patch, lowcostrayonexternal_v2.pdf
>
>
> YARN-1051 enables SLA support by allowing users to reserve cluster capacity 
> ahead of time. YARN-1710 introduced a greedy agent for placing user 
> reservations. The greedy agent makes fast placement decisions but at the cost 
> of ignoring the cluster committed resources, which might result in blocking 
> the cluster resources for certain periods of time, and in turn rejecting some 
> arriving jobs.
> We propose LowCost – a new cost-based planning algorithm. LowCost “spreads” 
> the demand of the job throughout the allowed time-window according to a 
> global, load-based cost function. 



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

Reply via email to