Hadoop QA commented on YARN-2972:

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {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:red}-1 findbugs{color}.  The patch appears to introduce 14 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:green}+1 core tests{color}.  The patch passed unit tests in 

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

This message is automatically generated.

> DelegationTokenRenewer thread pool never expands
> ------------------------------------------------
>                 Key: YARN-2972
>                 URL: https://issues.apache.org/jira/browse/YARN-2972
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: YARN-2972.001.patch
> DelegationTokenRenewer uses a thread pool to manage token renewals.  The 
> number of threads is configurable, but unfortunately the pool never expands 
> beyond the hardcoded initial 5 threads because we are using an unbounded 
> LinkedBlockingQueue.  ThreadPoolExecutor only grows the thread pool beyond 
> the core size when the specified queue is full.

This message was sent by Atlassian JIRA

Reply via email to