[
https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429978#comment-16429978
]
kyungwan nam commented on YARN-8095:
------------------------------------
Hi. [~cheersyang]
{quote}
yarn.scheduler.capacity.root.batch.priority=0
yarn.scheduler.capacity.root.batch.capacity=50
yarn.scheduler.capacity.root.batch.maximum-capacity=100
yarn.scheduler.capacity.root.longlived.priority=1
yarn.scheduler.capacity.root.longlived.capacity=50
yarn.scheduler.capacity.root.longlived.maximum-capacity=50
{quote}
Therefore, my config is as follows.
||Queue||Priority||Capacity||Accessible-Partition||
|root.longlived| 1 | 50~50 | default |
|root.batch| 0 | 50~100 | default |
|root.label1| 0 | 0 | label1 |
> Allow disable non-exclusive allocation
> --------------------------------------
>
> Key: YARN-8095
> URL: https://issues.apache.org/jira/browse/YARN-8095
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Affects Versions: 2.8.3
> Reporter: kyungwan nam
> Priority: Major
>
> We have 'longlived' Queue, which is used for long-lived apps.
> In situation where default Partition resources are not enough, containers for
> long-lived app can be allocated to sharable Partition.
> Since then, containers for long-lived app can be easily preempted.
> We don’t want long-lived apps to be killed abruptly.
> Currently, non-exclusive allocation can happen regardless of whether the
> queue is accessible to the sharable Partition.
> It would be good if non-exclusive allocation can be disabled at queue level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
