hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6918) Remove acls after queue delete to avoid memory leak
Date Fri, 29 Dec 2017 09:53:00 GMT

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

Sunil G commented on YARN-6918:

Yes. Lets move forward here.
It makes sense to have {{removePermission}} to clean up acls post queue delete. (by using
new queue management feature)

Few comments
# Why removePermission needs ugi as second param?
# Pls remove {{import java.util.*;}} and add necessary imports from util

> Remove acls after queue delete to avoid memory leak
> ---------------------------------------------------
>                 Key: YARN-6918
>                 URL: https://issues.apache.org/jira/browse/YARN-6918
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>         Attachments: YARN-6918.001.patch
> Acl for deleted queue need to removed from allAcls to avoid leak (Priority,YarnAuthorizer)

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