Hadoop QA commented on YARN-3472:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 174d8b3.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 


Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7317//console

This message is automatically generated.

> Possible leak in DelegationTokenRenewer#allTokens 
> --------------------------------------------------
>                 Key: YARN-3472
>                 URL: https://issues.apache.org/jira/browse/YARN-3472
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Rohith
>         Attachments: 0001-YARN-3472.patch, 0002-YARN-3472.patch
> When old token is expiring and being removed, it's not removed from the 
> allTokens map, resulting in possible leak. 
> {code}
> if (t.token.getKind().equals(new Text("HDFS_DELEGATION_TOKEN"))) {
>               iter.remove();
>               t.cancelTimer();
>               LOG.info("Removed expiring token " + t);
>             }
> {code}

This message was sent by Atlassian JIRA

Reply via email to