kyungwan nam commented on YARN-8095:

Hi [~cheersyang]
Yes. that’d resolve the problem. besides, it looks make sense.
Currently, in case of *non-exclusive allocation*, checking the 
accessible-node-lables is skipped.

synchronized (this) {
  // if our queue cannot access this node, just return
  if (schedulingMode == SchedulingMode.RESPECT_PARTITION_EXCLUSIVITY
      && !accessibleToPartition(node.getPartition())) {
    return CSAssignment.NULL_ASSIGNMENT;



> 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

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