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

Hudson commented on YARN-3497:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #2102 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2102/])
YARN-3497. ContainerManagementProtocolProxy modifies IPC timeout conf without 
making a copy. Contributed by Jason Lowe (jianhe: rev 
f967fd2f21791c5c4a5a090cc14ee88d155d2e2b)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/impl/ContainerManagementProtocolProxy.java
* hadoop-yarn-project/CHANGES.txt


> 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
>             Fix For: 2.7.1
>
>         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
(v6.3.4#6332)

Reply via email to