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 "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2016/07/14 03:12:20 UTC
[jira] [Comment Edited] (YARN-5342) Improve non-exclusive node
partition resource allocation in Capacity Scheduler
[ https://issues.apache.org/jira/browse/YARN-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375771#comment-15375771 ]
Naganarasimha G R edited comment on YARN-5342 at 7/14/16 3:11 AM:
------------------------------------------------------------------
Thanks for the patch [~wangda],
Given that discussed approach in YARN-4425 (Fallback Policy based ) is going to take some time as it would require significant modifications, i would agree to go for intermittent modification to optimize the non exclusive mode scheduling.
Only concern i have is if the size of default partition is greater than the non exclusive partition then on one allocation in default we are resetting the counter, would it be productive ?
was (Author: naganarasimha):
Thanks for the patch [~wangda],
Given that discussed approach in YARN-4225 (Fallback Policy based ) is going to take some time as it would require significant modifications, i would agree to go for intermittent modification to optimize the non exclusive mode scheduling.
Only concern i have is if the size of default partition is greater than the non exclusive partition then on one allocation in default we are resetting the counter, would it be productive ?
> Improve non-exclusive node partition resource allocation in Capacity Scheduler
> ------------------------------------------------------------------------------
>
> Key: YARN-5342
> URL: https://issues.apache.org/jira/browse/YARN-5342
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-5342.1.patch
>
>
> In the previous implementation, one non-exclusive container allocation is possible when the missed-opportunity >= #cluster-nodes. And missed-opportunity will be reset when container allocated to any node.
> This will slow down the frequency of container allocation on non-exclusive node partition: *When a non-exclusive partition=x has idle resource, we can only allocate one container for this app in every X=nodemanagers.heartbeat-interval secs for the whole cluster.*
> In this JIRA, I propose a fix to reset missed-opporunity only if we have >0 pending resource for the non-exclusive partition OR we get allocation from the default partition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org