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 "Sunil Govindan (JIRA)" <ji...@apache.org> on 2019/07/03 07:02:00 UTC
[jira] [Comment Edited] (YARN-9662) Preemption not working on
NodeLabels
[ https://issues.apache.org/jira/browse/YARN-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877538#comment-16877538 ]
Sunil Govindan edited comment on YARN-9662 at 7/3/19 7:01 AM:
--------------------------------------------------------------
[~Amithsha] hadoop-2.7 doesnt support label based preemption, and YARN-7685 was about that.
Cud u pls confirm the version ?
was (Author: sunilg):
[~Amithsha] hadoop-2.7 doesnt support label based preemption, and YARN-7685 was about that.
Cud u pls conform the version ?
> Preemption not working on NodeLabels
> ------------------------------------
>
> Key: YARN-9662
> URL: https://issues.apache.org/jira/browse/YARN-9662
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Amithsha
> Priority: Major
>
> Preemption on node labels is not working when the utilization is 100%.
> Example
> adhocp0,adhocp1,adhocp3 Queues mapped to nodelabels of label_adhoc_nm.
> With a share of 60,30,10 as actual capacity and 100 as maximum capacity for all.
> When a jobA on adhocp3 consumes 100% of its maximum capacity and a jobB submitted on adhocp0 no containers running on adhocp3 queue got preempted.
>
> This is already reported by another user
> https://issues.apache.org/jira/browse/YARN-7685
> Note :
> Jobs with more than actual capacity and less than the maximum capacity are able to preempt the containers.
--
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