[
https://issues.apache.org/jira/browse/YARN-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-376:
----------------------------
Attachment: YARN-376.patch
Thanks for the review, Sidd. I originally had it update the heartbeat since
the RMNode interface already knew about the heartbeat type and it's more
efficient (don't need to create an extra copy of the app list and grab the
write lock only once instead of twice).
Updated to change get*ToCleanup to pull*ToCleanup and test no longer needs the
heartbeat response since it no longer updates it directly.
> 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.patch, YARN-376.patch, YARN-376.patch
>
>
> 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
