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

Posted to issues@tez.apache.org by "Chang Li (JIRA)" <ji...@apache.org> on 2015/04/17 22:45:59 UTC

[jira] [Commented] (TEZ-2334) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

Chang Li commented on TEZ-2334:
-------------------------------

[~jlowe], [~hitesh], could you help review this patch? Thanks

> ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy
> --------------------------------------------------------------------------------
>
>                 Key: TEZ-2334
>                 URL: https://issues.apache.org/jira/browse/TEZ-2334
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: TEZ-2334.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. relate to YARN-3297. This is a work around for tez running on 2.6 and 2.7.0 grids.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)