Hadoop QA commented on YARN-3497:

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

    {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: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:green}+1 core tests{color}.  The patch passed unit tests in 

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

This message is automatically generated.

> ContainerManagementProtocolProxy modifies IPC timeout conf without making a 
> copy
> --------------------------------------------------------------------------------
>                 Key: YARN-3497
>                 URL: https://issues.apache.org/jira/browse/YARN-3497
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: YARN-3497.001.patch, YARN-3497.002.patch
> yarn-client's ContainerManagementProtocolProxy is updating 
> ipc.client.connection.maxidletime in the conf passed in without making a copy 
> of it. That modification "leaks" into other systems using the same conf and 
> can cause them to setup RPC connections with a timeout of zero as well.

This message was sent by Atlassian JIRA

Reply via email to