Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 1 Mar 2013 05:57:15 +0000 (UTC)
From: "Siddharth Seth (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12630733.1360006393316.363066.1362117435545@arcas>
In-Reply-To: <JIRA.12630733.1360006393316@arcas>
References: <JIRA.12630733.1360006393316@arcas>
Subject: [jira] [Commented] (YARN-376) Apps that have completed can appear
 as RUNNING on the NM UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siddharth Seth commented on YARN-376:
-------------------------------------

The eclipse failures is not related. Committing this.
                
> Apps that have completed can appear as RUNNING on the NM UI
> -----------------------------------------------------------
>
>                 Key: YARN-376
>                 URL: https://issues.apache.org/jira/browse/YARN-376
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.3-alpha, 0.23.6
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>         Attachments: YARN-376_branch-0.23.txt, YARN-376.patch, YARN-376.patch, YARN-376.patch, YARN-376.patch, YARN-376-trunk.txt
>
>
> On a busy cluster we've noticed a growing number of applications appear as RUNNING on a nodemanager web pages but the applications have long since finished.  Looking at the NM logs, it appears the RM never told the nodemanager that the application had finished.  This is also reflected in a jstack of the NM process, since many more log aggregation threads are running then one would expect from the number of actively running applications.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira