hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (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 18:59:07 GMT

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

Vinod Kumar Vavilapalli commented on YARN-3445:

bq. I agree. This shouldn't be needed anymore after YARN-1402. I had the similar idea before
in synced with Xuan but forget to put it on JIRA. May be we should file a separated JIRA to
fix it?
keepAliveApplications cannot be removed as we need to support protocol compatibility. But
the new ones you added for logs can be removed as they are new. Can you take this forward
also on YARN-3505?

bq. .. LogAggregationReport#(get/set)getNodeId .. LogAggregationReport#(get/set)DiagnosticMessage
[~jianhe], can you file a ticket please?

> 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

This message was sent by Atlassian JIRA

View raw message