Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 28 Aug 2015 07:23:46 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12848839.1437727908000.191569.1440746626026@Atlassian.JIRA>
In-Reply-To: <JIRA.12848839.1437727908000@Atlassian.JIRA>
References: <JIRA.12848839.1437727908000@Atlassian.JIRA>
 <JIRA.12848839.1437727908910@arcas>
Subject: [jira] [Commented] (YARN-3970) REST api support for Application
 Priority
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718143#comment-14718143 ] 

Sunil G commented on YARN-3970:
-------------------------------

Hi Naga.
Yes.  I could see that you are planning to use {{getClientRMService}}.
That saves the direct api invocation to AbstractYarnScheduler. This looks
fine as all validation are handled.
Thank You.

On Fri, Aug 28, 2015, 12:38 PM Naganarasimha G R (JIRA) <jira@apache.org>


> REST api support for Application Priority
> -----------------------------------------
>
>                 Key: YARN-3970
>                 URL: https://issues.apache.org/jira/browse/YARN-3970
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: webapp
>    Affects Versions: 2.7.1
>            Reporter: Sunil G
>            Assignee: Naganarasimha G R
>
> REST api support for application priority.
> - get/set priority of an application
> - get default priority of a queue
> - get cluster max priority


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