[
https://issues.apache.org/jira/browse/YARN-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500873#comment-14500873
]
Jian He commented on YARN-3497:
-------------------------------
should we change below to use this.conf as well ?
{code}
conf.setInt(
CommonConfigurationKeysPublic.IPC_CLIENT_CONNECTION_MAXIDLETIME_KEY,
0);
{code}
> 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-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)
