[
https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520396#comment-14520396
]
Vinod Kumar Vavilapalli commented on YARN-3445:
-----------------------------------------------
There is a too much of duplicate information already in NodeHeartbeatRequest,
albeit for slightly different purposes. We need to consolidate the following
(without breaking compatibility of previous releases), lest the heartbeat will
become heavier and heavier.
- logAggregationReportsForApps added, but not released yet
-- logAggregationReportsForApps itself is a map of ApplicationID with a
nested LogAggregationReport.ApplicationID - duplicate AppID information
- runningApplications in this patch
- NodeStatus.keepAliveApplications
/cc [~jianhe] [~leftnoteasy]
> 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)
