[
https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422254#comment-16422254
]
Weiwei Yang commented on YARN-8095:
-----------------------------------
Hi [~kyungwan nam]
This is interesting.
Can you please elaborate the configs you used? Not paste all configs, but
briefly demonstrate how it is configured like what's the accessible labels and
capacity of long-lived queue/batch queue. That will help us to understand your
scenario. It looks to me like this problem doesn't necessarily be resolved with
partitions, it looks more like a preemption problem to me. Anyway, please share
more info so we can discuss in depth.
I am adding [~leftnoteasy], [~sunilg] and [~Tao Yang] as they are experts on
this area.
> 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
