hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subru Krishnan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6565) Fix memory leak and finish app trigger in AMRMProxy
Date Fri, 05 May 2017 21:29:04 GMT

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

Subru Krishnan commented on YARN-6565:

[~botong], good catch! The patch LGTM, can you fix the minor checkstyle issue so that I commit
it. Thanks.

> 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
>         Attachments: YARN-6565.v1.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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message