You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/04/16 19:58:58 UTC

[jira] [Updated] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

     [ https://issues.apache.org/jira/browse/YARN-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated YARN-3497:
-----------------------------
    Attachment: YARN-3497.001.patch

This causes the Tez AM to reconnect to the RM on every AM heartbeat.

Patch to create a copy of the configuration when initializing the proxy cache.

> 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)