hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId
Date Thu, 30 Apr 2015 17:25:08 GMT

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

Jian He commented on YARN-3445:
-------------------------------

One other thing, the LogAggregationReport#(get/set)getNodeId can also be removed as it's not
used anywhere. 
I'm also unsure about the usage of LogAggregationReport#(get/set)DiagnosticMessage as it's
only set with an empty string.

agree we can have a separate jira to fix this, preferably  in the same 2.8 release.



> 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)

Mime
View raw message