Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 29 Jan 2015 19:01:36 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12711429.1398851241000.207457.1422558096553@Atlassian.JIRA>
In-Reply-To: <JIRA.12711429.1398851241000@Atlassian.JIRA>
References: <JIRA.12711429.1398851241000@Atlassian.JIRA>
 <JIRA.12711429.1398851241331@arcas>
Subject: [jira] [Updated] (YARN-2003) Support to process Job priority from
 Submission Context in AppAttemptAddedSchedulerEvent [RM side]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sunil G updated YARN-2003:
--------------------------
    Attachment: 0001-YARN-2003.patch

Uploading an initial prototype patch for RM changes needed for application priority.

This patch is based on existing PriorityLabelManager. As per the discussion, there may be some more changes in that JIRA. Hence this patch will be rebased as per same.

Kindly check and share your comments.


> Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]
> --------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2003
>                 URL: https://issues.apache.org/jira/browse/YARN-2003
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-2003.patch
>
>
> AppAttemptAddedSchedulerEvent should be able to receive the Job Priority from Submission Context and store.
> Later this can be used by Scheduler.


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