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 "kyungwan nam (JIRA)" <ji...@apache.org> on 2018/08/27 12:28:00 UTC
[jira] [Commented] (YARN-8095) Allow disable non-exclusive
allocation
[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593584#comment-16593584 ]
kyungwan nam commented on YARN-8095:
------------------------------------
[~leftnoteasy], Sorry for bothering you. but could you share your thoughts?
Thanks
> 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
> Attachments: YARN-8095-branch-2.8.001.patch
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org