From yarn-issues-return-171384-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Aug 22 19:16:02 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1CC36180644 for ; Thu, 22 Aug 2019 21:16:02 +0200 (CEST) Received: (qmail 89074 invoked by uid 500); 22 Aug 2019 19:16:01 -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 89053 invoked by uid 99); 22 Aug 2019 19:16:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2019 19:16:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B6A21E308B for ; Thu, 22 Aug 2019 19:16:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 2AF70780A64 for ; Thu, 22 Aug 2019 19:16:00 +0000 (UTC) Date: Thu, 22 Aug 2019 19:16:00 +0000 (UTC) From: "Jonathan Hung (Jira)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-9760) Support configuring application priorities on a workflow level 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-9760?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16913= 621#comment-16913621 ]=20 Jonathan Hung commented on YARN-9760: ------------------------------------- Hi [~eepayne], thanks for the comments. I understand the concern. The reaso= n we implemented it this way was b/c we wanted queue admins to be able to s= et workflow priorities themselves (i.e. leveraging YARN queue ACLs) which w= ould be difficult to do client-side. IMO there's not too much complexity for this feature on the RM side. But to= minimize overall complexity, perhaps we can do this in a way that doesn't = make protocol changes, and on the RM side we can leverage the queue mapping= interface. Would this address your concerns? [~varun_saxena] how does this= sound? > Support configuring application priorities on a workflow level > -------------------------------------------------------------- > > Key: YARN-9760 > URL: https://issues.apache.org/jira/browse/YARN-9760 > Project: Hadoop YARN > Issue Type: New Feature > Reporter: Jonathan Hung > Assignee: Varun Saxena > Priority: Major > Labels: release-blocker > > Currently priorities are submitted on an application level, but for end u= sers it's common to submit workloads to YARN at a workflow level. This=C2= =A0jira proposes a feature to store workflow id + priority mappings on RM (= similar to queue mappings). If app is submitted with a certain workflow id = (as set in application submission context) RM will override this app's prio= rity with the one defined in the mapping. -- This message was sent by Atlassian Jira (v8.3.2#803003) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org