You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/05/05 00:30:07 UTC
[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for
getting running apps on given NodeId
[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527480#comment-14527480 ]
Vinod Kumar Vavilapalli commented on YARN-3445:
-----------------------------------------------
With those comments out of the way, the patch looks good to me. But I'd still like to see a follow up JIRA and a patch that depend on this. Just to make sure we have it the right way.
> Cache runningApps in RMNode for getting running apps on given NodeId
> --------------------------------------------------------------------
>
> Key: YARN-3445
> URL: https://issues.apache.org/jira/browse/YARN-3445
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Affects Versions: 2.7.0
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: YARN-3445-v2.patch, YARN-3445.patch
>
>
> Per discussion in YARN-3334, we need filter out unnecessary collectors info from RM in heartbeat response. Our propose is to add cache for runningApps in RMNode, so RM only send collectors for local running apps back. This is also needed in YARN-914 (graceful decommission) that if no running apps in NM which is in decommissioning stage, it will get decommissioned immediately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)