From yarn-issues-return-137970-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Feb 15 04:25:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id C5729180621 for ; Thu, 15 Feb 2018 04:25:04 +0100 (CET) Received: (qmail 64194 invoked by uid 500); 15 Feb 2018 03:25:03 -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 64183 invoked by uid 99); 15 Feb 2018 03:25:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 03:25:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 2F887C22A4 for ; Thu, 15 Feb 2018 03:25:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id RipGw1M1tEuz for ; Thu, 15 Feb 2018 03:25: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 2ADCB5F576 for ; Thu, 15 Feb 2018 03:25: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 307DCE02F7 for ; Thu, 15 Feb 2018 03:25: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 5A27721E65 for ; Thu, 15 Feb 2018 03:25:00 +0000 (UTC) Date: Thu, 15 Feb 2018 03:25:00 +0000 (UTC) From: "genericqa (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7292) Revisit Resource Profile Behavior MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-7292?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16365= 099#comment-16365099 ]=20 genericqa commented on YARN-7292: --------------------------------- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s= {color} | {color:blue} Docker mode activated. {color} | | {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{co= lor} | {color:red} YARN-7292 does not apply to trunk. Rebase required? Wron= g Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {col= or} | \\ \\ || Subsystem || Report/Notes || | JIRA Issue | YARN-7292 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/1291016= 4/YARN-7292.006.patch | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/19699= /console | | Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org | This message was automatically generated. > Revisit Resource Profile Behavior > --------------------------------- > > Key: YARN-7292 > URL: https://issues.apache.org/jira/browse/YARN-7292 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Wangda Tan > Assignee: Wangda Tan > Priority: Blocker > Attachments: YARN-7292.002.patch, YARN-7292.003.patch, YARN-7292.= 004.patch, YARN-7292.005.patch, YARN-7292.006.patch, YARN-7292.wip.001.patc= h > > > Had discussions with [~templedf], [~vvasudev], [~sunilg] offline. There'r= e a couple of resource profile related behaviors might need to be updated: > 1) Configure resource profile in server side or client side:=20 > Currently resource profile can be only configured centrally: > - Advantages: > A given resource profile has a the same meaning in the cluster. It won=E2= =80=99t change when we run different apps in different configurations. A jo= b can run under Amazon=E2=80=99s G2.8X can also run on YARN with G2.8X prof= ile. A side benefit is YARN scheduler can potentially do better bin packing= . > - Disadvantages:=20 > Hard for applications to add their own resource profiles.=20 > 2) Do we really need mandatory resource profiles such as minimum/maximum/= default?=20 > 3) Should we send resource profile name inside ResourceRequest, or should= client/AM translate it to resource and set it to the existing resource fie= lds?=20 > 4) Related to above, should we allow resource overrides or client/AM shou= ld send final resource to RM? -- 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