Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 12 Jan 2016 20:08:39 +0000 (UTC)
From: "Naganarasimha G R (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12908588.1446044291000.89180.1452629319870@Atlassian.JIRA>
In-Reply-To: <JIRA.12908588.1446044291000@Atlassian.JIRA>
References: <JIRA.12908588.1446044291000@Atlassian.JIRA>
 <JIRA.12908588.1446044291758@arcas>
Subject: [jira] [Updated] (YARN-4307) Blacklisted nodes for AM container is
 not getting displayed in the Web UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Naganarasimha G R updated YARN-4307:
------------------------------------
    Attachment: YARN-4307.v1.002.patch

Hi [~vvasudev],
I have uploaded a new patch with modifications for your comments
bq. Can we add the AM blacklisted nodes and the nodes blacklisted by the RM in to the app attempt info and expose both of these via webservices? Both fields should be a part of the rmAppAttempt.
earlier patch was also exposing these info in  app attempt info. In the latest patch have taken case for {{RMAppAttempt}}

> Blacklisted nodes for AM container is not getting displayed in the Web UI
> -------------------------------------------------------------------------
>
>                 Key: YARN-4307
>                 URL: https://issues.apache.org/jira/browse/YARN-4307
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, webapp
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>         Attachments: AppInfoPage.png, RMappAttempt.png, YARN-4307.v1.001.patch, YARN-4307.v1.002.patch, webpage.png, yarn-capacity-scheduler-debug.log
>
>
> In pseudo cluster had 2 NM's  and had launched app with incorrect configuration *./hadoop org.apache.hadoop.mapreduce.SleepJob -Dmapreduce.job.node-label-expression=labelX  -Dyarn.app.mapreduce.am.env=JAVA_HOME=/no/jvm/here  -m 5 -mt 1200*.
> First attempt failed and 2nd attempt was launched, but the application was hung. In the scheduler logs found that localhost was blacklisted but in the UI (app& apps listing page) count was shown as zero and as well no hosts listed in the app page. 


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