Return-Path: 
 <yarn-issues-return-76403-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 38864180B3
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Tue, 22 Dec 2015 18:47:47 +0000 (UTC)
Received: (qmail 11713 invoked by uid 500); 22 Dec 2015 18:47:47 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 11668 invoked by uid 500); 22 Dec 2015 18:47:47 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 11603 invoked by uid 99); 22 Dec 2015 18:47:46 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2015 18:47:46 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id BF0BB2C1F69
	for <yarn-issues@hadoop.apache.org>; Tue, 22 Dec 2015 18:47:46 +0000 (UTC)
Date: Tue, 22 Dec 2015 18:47:46 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12860911.1441090128000.95235.1450810066779@Atlassian.JIRA>
In-Reply-To: <JIRA.12860911.1441090128000@Atlassian.JIRA>
References: <JIRA.12860911.1441090128000@Atlassian.JIRA>
 <JIRA.12860911.1441090128956@arcas>
Subject: [jira] [Commented] (YARN-4098) Document ApplicationPriority feature
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-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068535#comment-15068535 ] 

Sunil G commented on YARN-4098:
-------------------------------

Hi [~rohithsharma]
Thank you for sharing the patch.

Some minor nits.
CS Page:
1. 
{noformat}
Higher the integer higher the priority of an applications. Note : Application priority is supported only for FIFO ordering policy.
{noformat}
Could we rephrase this as {{Higher integer value indicates higher priority for the application. Currently Application priority is supported only for FIFO ordering policy.}}

2. {{Application priority works along with FIFO ordering policy only}} can be {{Application priority works *only* along with FIFO ordering policy}}
3. {{Default priority for an applications can be at cluster level and queue level.}} its better to mention as {{an application}}.
4. Missing */* in {{etc/hadoop/capacity-scheduler.xml}}
5. typo in {{yarn.scheduler.capacity.root.<leaf-queue-patch>.default-application-priority}}. it can be {{<leaf-queue-path>}}

> Document ApplicationPriority feature
> ------------------------------------
>
>                 Key: YARN-4098
>                 URL: https://issues.apache.org/jira/browse/YARN-4098
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-4098.patch, 0001-YARN-4098.patch, YARN-4098.rar
>
>
> This JIRA is to track documentation of application priority and its user, admin and REST interfaces.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)