[
https://issues.apache.org/jira/browse/TEZ-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951185#comment-14951185
]
Hitesh Shah commented on TEZ-2872:
----------------------------------
bq. If all user payloads are combined into a local resource at the dag level
In this case, but this too depends on whether the spec is modified by any of
the vertex managers.
> Tez AM can be overwhelmed by TezTaskUmbilicalProtocol.getTask responses
> -----------------------------------------------------------------------
>
> Key: TEZ-2872
> URL: https://issues.apache.org/jira/browse/TEZ-2872
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jason Lowe
>
> When a large job runs on a large cluster with a large user payload then the
> AM can end up hitting OOM conditions. For example, Pig-on-Tez can require a
> significant user payload (approaching 1MB) for vertices, inputs, and outputs
> in the DAG. This can cause the ContainerTask response to be rather large per
> task, which can lead to a situation where the AM is generating output faster
> than the network interface can process it. If there are enough containers
> asking for tasks then this leads to an OOM condition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
