[
https://issues.apache.org/jira/browse/TEZ-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500674#comment-14500674
]
Jonathan Eagles commented on TEZ-2334:
--------------------------------------
Without this work around patch in tez, Tez AM's put a much higher load on the
RM due to breaking down the ContainerManager connection with each heartbeat.
(default 1 per/second). This will be a good patch for 0.5.x/0.6.x/0.7.x until
minimal hadoop version is 2.7.1.
Jon
> 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)
