From yarn-issues-return-138842-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Wed Feb 28 23:32:04 2018 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 692F818A78 for ; Wed, 28 Feb 2018 23:32:04 +0000 (UTC) Received: (qmail 41483 invoked by uid 500); 28 Feb 2018 23:32:04 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 41402 invoked by uid 500); 28 Feb 2018 23:32:04 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 41372 invoked by uid 99); 28 Feb 2018 23:32:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Feb 2018 23:32:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 97F6AC0090 for ; Wed, 28 Feb 2018 23:32:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id A2Ja98ZAh92W for ; Wed, 28 Feb 2018 23:32:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 03D535FB92 for ; Wed, 28 Feb 2018 23:32:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 64EEFE0950 for ; Wed, 28 Feb 2018 23:32:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 82CE82476E for ; Wed, 28 Feb 2018 23:32:00 +0000 (UTC) Date: Wed, 28 Feb 2018 23:32:00 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7972) Support inter-app placement constraints for allocation tags by application ID MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381234#comment-16381234 ] Arun Suresh commented on YARN-7972: ----------------------------------- Thanks for the patch [~cheersyang] I see that currently you do not have an implementation for the not-self and all. I am guessing, that is because it would require changes in the AllocationTagsManager as well - to aggregate the cardinality across applicationIds. I am fine punting that to a separate JIRA given the complexity, but maybe you can add support for it in the namespace parser and then throw an exception in the PCUtils class that it is not supported. As for the {{ns:}} prefix, I don't really mind it (given it is very short), but to [~leftnoteasy]'s point, we should either use {{ns:}} or the {{yarn_application_label/}} prefix and remove the other. > Support inter-app placement constraints for allocation tags by application ID > ----------------------------------------------------------------------------- > > Key: YARN-7972 > URL: https://issues.apache.org/jira/browse/YARN-7972 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Weiwei Yang > Assignee: Weiwei Yang > Priority: Major > Attachments: YARN-7972.001.patch, YARN-7972.002.patch > > > Per discussion in [this comment|https://issues.apache.org/jira/browse/YARN-6599focusedCommentId=16319662&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16319662] in YARN-6599, we need to support inter-app PC for allocation tags. > This will help to do better placement when dealing with potential competing resource applications, e.g don't place two tensorflow workers from two different applications on one same node. -- 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