[
https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301055#comment-15301055
]
Daniel Templeton commented on YARN-5035:
----------------------------------------
Thanks for the patch, [~kasha]. Looks to me like you can never assign the last
container on a node because {{Resources.multiplyTo()}} will round down. Also
you have an "upto" in the MD code that you should fix.
Maybe I'm backseat designing a bit, but I wonder if it would be useful to have
a configurable minimum to the dynamic assign. I could see it being useful to
say I want to schedule half the node or 2 containers, which ever is more.
> FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on
> ----------------------------------------------------------------------------
>
> Key: YARN-5035
> URL: https://issues.apache.org/jira/browse/YARN-5035
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: fairscheduler
> Affects Versions: 2.8.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: yarn-5035-1.patch
>
>
> When assignMultiple is turned on, today the number of containers allocated to
> node within a single heartbeat is determined by maxAssign. Picking a higher
> value for this prevents the spreading of the workload, and a smaller number
> leads to slow ramp up.
> The proposal is to make it dynamic - half of the unallocated resources on the
> node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
