Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 27 Aug 2014 02:44:58 +0000 (UTC)
From: "Maysam Yabandeh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12733314.1407781834452.20266.1409107498193@arcas>
In-Reply-To: <JIRA.12733314.1407781834452@arcas>
References: <JIRA.12733314.1407781834452@arcas>
Subject: [jira] [Commented] (YARN-2405) NPE in FairSchedulerAppsBlock
 (scheduler page)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Maysam Yabandeh commented on YARN-2405:
---------------------------------------

Sounds good to me. We also need to decide of how to react to nonexistent app: return fair share of 0, -1, or skip the whole record from appsTableData? If the the problematic record is going to be skipped, instead of putting checks inside fair share computation, we can alternatively catch the NPE at FairSchedulerAppsBlock.

> NPE in FairSchedulerAppsBlock (scheduler page)
> ----------------------------------------------
>
>                 Key: YARN-2405
>                 URL: https://issues.apache.org/jira/browse/YARN-2405
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Maysam Yabandeh
>
> FairSchedulerAppsBlock#render throws NPE at this line
> {code}
>       int fairShare = fsinfo.getAppFairShare(attemptId);
> {code}
> This causes the scheduler page now showing the app since it lack the definition of appsTableData
> {code}
>  Uncaught ReferenceError: appsTableData is not defined 
> {code}
> The problem is temporary meaning that it is usually resolved by itself either after a retry or after a few hours.


--
This message was sent by Atlassian JIRA
(v6.2#6252)