hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId
Date Tue, 07 Jul 2015 14:13:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Junping Du updated YARN-3445:
-----------------------------
    Attachment: YARN-3445-v5.patch

bq. It looks like RMNodeImpl's handle function already takes write lock for any state transition,
and these private methods will only be invoked from state transition functions.
Nice catch, [~mingma]! I could miss the lock in the caller, so remove unnecessary write lock
in v5 patch.

> 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-v3.1.patch, YARN-3445-v3.patch, YARN-3445-v4.1.patch,
YARN-3445-v4.patch, YARN-3445-v5.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