[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430190#comment-16430190 ]
kyungwan nam commented on YARN-8095: ------------------------------------ I don't think that's a bug. an app with ‘label1’ node-label must get the preference on ‘lable1’ partition. therefore, containers, which are placed on ‘label1’ partition by non-exclusive allocation should be preempted firstly. IMHO, rather than preemption problem, I think the way to disable non-exclusive allocation should be provided. > 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