You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/07/07 19:46:11 UTC

[jira] [Updated] (TEZ-3286) Allow clients to set processor reserved memory per vertex (instead of per container)

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

Hitesh Shah updated TEZ-3286:
-----------------------------
    Attachment: TEZ-3286.3.branch-07.patch

> Allow clients to set processor reserved memory per vertex (instead of per container)
> ------------------------------------------------------------------------------------
>
>                 Key: TEZ-3286
>                 URL: https://issues.apache.org/jira/browse/TEZ-3286
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.8.3
>            Reporter: Wei Zheng
>            Assignee: Hitesh Shah
>             Fix For: 0.9.0, 0.8.4
>
>         Attachments: TEZ-3286.1.patch, TEZ-3286.2.patch, TEZ-3286.3.branch-07.patch, TEZ-3286.3.patch, TEZ-3286.3.withTestTimeout.txt
>
>
> tez.task.scale.memory.reserve-fraction can be set by clients to control how much memory is available to the processor. Ths values applies at a container level though, instead of at a vertex level.
> In case of a hash-join - the processor typically needs more memory. In case of  a Shuffle join - the processor may not need as much. In DAGs with a mix of map joins and shuffle joins - setting this at a container level is sub-optimal.
> To a large extent this comes down to propagating vertex configs to the container / task.



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