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 A060519F85 for ; Wed, 20 Apr 2016 02:00:30 +0000 (UTC) Received: (qmail 9297 invoked by uid 500); 20 Apr 2016 02:00:30 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 9244 invoked by uid 500); 20 Apr 2016 02:00:30 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 9196 invoked by uid 99); 20 Apr 2016 02:00:30 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 02:00:30 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0AAB82C1F64 for ; Wed, 20 Apr 2016 02:00:30 +0000 (UTC) Date: Wed, 20 Apr 2016 02:00:30 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4023) Publish Application Priority to TimelineServer 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-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249116#comment-15249116 ] Sunil G commented on YARN-4023: ------------------------------- HI [~jianhe], I have checked below code in {{RMAppManager.createAndPopulateNewRMApp}}. With this piece of code, even if priority is NOT set in submissionContext, we will set it with a default priority for any apps (with 0 priority in dflt case). This will not impact any apps untill we enable app priority from top level. {code} // Verify and get the update application priority and set back to // submissionContext Priority appPriority = rmContext.getScheduler() .checkAndGetApplicationPriority(submissionContext.getPriority(), user, submissionContext.getQueue(), applicationId); submissionContext.setPriority(appPriority); {code} This same code is invoked from {{recoverApplication}} also. So even in rolling upgrade cases where app is saved to Store w/o priority in submission context, it will be added wth a priority 0 with above piece of code during recovery. [~jianhe] will this be fine? or do you see some other problem because of this. pls share your feedback. > Publish Application Priority to TimelineServer > ---------------------------------------------- > > Key: YARN-4023 > URL: https://issues.apache.org/jira/browse/YARN-4023 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Sunil G > Assignee: Sunil G > Fix For: 2.8.0 > > Attachments: 0001-YARN-4023.patch, 0001-YARN-4023.patch, ApplicationPage.png, TimelineserverMainpage.png > > > Publish Application priority details to Timeline Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)