[jira] [Commented] (YARN-5342) Improve non-exclusive node partition resource allocation in Capacity Scheduler

["Naganarasimha G R (JIRA)" <ji...@apache.org>]

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

Naganarasimha G R commented on YARN-5342:
-----------------------------------------

Thanks for attaching the patch for 2.8, seems like jenkins run is fine, Test case failures are not related to the patch.
 [~wangda] can you commit patch and resolve this jira ?

> 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: Sunil G
>         Attachments: YARN-5342-branch-2.8.001.patch, YARN-5342.1.patch, YARN-5342.2.patch, YARN-5342.3.patch, YARN-5342.4.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