Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 20 Jan 2016 05:47:39 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12922949.1450421639000.155004.1453268859919@Atlassian.JIRA>
In-Reply-To: <JIRA.12922949.1450421639000@Atlassian.JIRA>
References: <JIRA.12922949.1450421639000@Atlassian.JIRA>
 <JIRA.12922949.1450421639076@arcas>
Subject: [jira] [Commented] (YARN-4479) Retrospect app-priority in
 pendingOrderingPolicy during recovering applications
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sunil G commented on YARN-4479:
-------------------------------

Yes [~leftnoteasy], as mentioned by [~Naganarasimha Garla] , this option came up as a possible solution. However, there were few complexities:

For this approach, we Needed a new {{RecoveryComparator}}. This has to be added to {{FifoOrderingPolicy}} also. RecoveryComparator was supposed to run with the information that whether this app was running prior to recovery. So a flag has to be added to FicaSchedulerApp, and then reset the same after first round of activation. Hence more complexities in various part of scheduler was needed for this approach. So a simpler approach is made in LeafQueue. Pls share your thoughts if we missed any in this approach.
[~rohithsharma] Could u pls add if I missed any point for this approach.

> Retrospect app-priority in pendingOrderingPolicy during recovering applications
> -------------------------------------------------------------------------------
>
>                 Key: YARN-4479
>                 URL: https://issues.apache.org/jira/browse/YARN-4479
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, resourcemanager
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>             Fix For: 2.8.0
>
>         Attachments: 0001-YARN-4479.patch, 0002-YARN-4479.patch, 0003-YARN-4479.patch, 0004-YARN-4479.patch, 0004-YARN-4479.patch, 0005-YARN-4479.patch, 0006-YARN-4479.patch
>
>
> Currently, same ordering policy is used for pending applications and active applications. When priority is configured for an applications, during recovery high priority application get activated first. It is possible that low priority job was submitted and running state. 
> This causes low priority job in starvation after recovery


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