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

Weiwei Yang commented on YARN-8095:
-----------------------------------

Hi [~kyungwan nam]
{quote}therefore, containers, which are placed on ‘label1’ partition by 
non-exclusive allocation should be preempted firstly.
{quote}
I would expect it preempts containers from batch queue first. If it preempts 
resource from batch first then longlived, I would say that is working as 
expected. However if this is not a case, it sounds like a bug to me.
{quote}IMHO, rather than preemption problem, I think the way to disable 
non-exclusive allocation should be provided.
{quote}
Exclusive/non-exclusive currently is an attribute for node partition. What do 
you mean by disabling non-exclusive allocation? Could you elaborate your idea 
please?

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
>
> 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

Reply via email to