[jira] [Updated] (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:all-tabpanel ] Varun Saxena updated YARN-3445: --- Fix Version/s: 2.9.0 > Cache runningApps in RMNode for getting running apps on given NodeId > -

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445-v5.1.patch The unit test failures seems not be related, and the same test failure get

[jira] [Updated] (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: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

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445-v4.1.patch Fix check-style issue in v4.1 patch. > Cache runningApps in RMNode for ge

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445-v4.patch Update patch in v4 patch according to [~mingma]'s comments above. > Cache r

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445-v3.1.patch Rebase the patch to trunk. > Cache runningApps in RMNode for getting runn

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445-v3.patch Unit test failure should be unrelated. Fix checkstyle/whitespace/findbugs w

[jira] [Updated] (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:all-tabpanel ] Allen Wittenauer updated YARN-3445: --- Labels: BB2015-05-TBR (was: ) > Cache runningApps in RMNode for getting running apps on given

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445-v2.patch Update patch in v2 with new way proposed above. > Cache runningApps in RMNo

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Description: Per discussion in YARN-3334, we need filter out unnecessary collectors info from RM in heartbe

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3445: - Summary: Cache runningApps in RMNode for getting running apps on given NodeId (was: NM notify RM on runnin