[
https://issues.apache.org/jira/browse/YARN-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999162#comment-15999162
]
Hudson commented on YARN-6565:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11693 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11693/])
YARN-6565. Fix memory leak and finish app trigger in AMRMProxy. (Botong (subru:
rev d6eed5acca222a281401c1d524824f0460ea7826)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/amrmproxy/AMRMProxyService.java
* (add)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/amrmproxy/TestAMRMProxyTokenSecretManager.java
> Fix memory leak and finish app trigger in AMRMProxy
> ---------------------------------------------------
>
> Key: YARN-6565
> URL: https://issues.apache.org/jira/browse/YARN-6565
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Minor
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: YARN-6565.v1.patch, YARN-6565.v2.patch
>
>
> Two issues in AMRMProxy:
> 1. When application finishes, AMRMTokenSecretManager is not updated to remove
> related data, leading to memory leak.
> 2. When we kill an application, we should remove the pipeline after the AM
> container is killed.
> FINISH_APPLICATION event is sent when the AM container is still being killed.
> After we remove the pipeline, we might still get heartbeats from AM,
> triggering exception messages.
> Instead, we should wait for APPLICATION_RESOURCES_CLEANEDUP event, sent after
> where the AM container is killed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
