Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 25 Aug 2015 06:44:46 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12858517.1440479180000.155308.1440485086051@Atlassian.JIRA>
In-Reply-To: <JIRA.12858517.1440479180000@Atlassian.JIRA>
References: <JIRA.12858517.1440479180000@Atlassian.JIRA>
 <JIRA.12858517.1440479180467@arcas>
Subject: [jira] [Commented] (YARN-4078) Unchecked typecast to
 AbstractYarnScheduler in AppInfo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Varun Saxena commented on YARN-4078:
------------------------------------

In the main code, its guarded at places other than the issue raised here. 

> Unchecked typecast to AbstractYarnScheduler in AppInfo
> ------------------------------------------------------
>
>                 Key: YARN-4078
>                 URL: https://issues.apache.org/jira/browse/YARN-4078
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>            Priority: Minor
>
> Currently getPendingResourceRequestForAttempt is present in {{AbstractYarnScheduler}}.
> *But in AppInfo,  we are calling this method by typecasting it to AbstractYarnScheduler, which is incorrect.*
> Because if a custom scheduler is to be added, it will implement YarnScheduler, not AbstractYarnScheduler.
> This method should be moved to YarnScheduler or it should have a guarded check like in other places (RMAppAttemptBlock.getBlackListedNodes) 


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