[
https://issues.apache.org/jira/browse/TEZ-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358113#comment-15358113
]
TezQA commented on TEZ-3286:
----------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12815571/TEZ-3286.3.withTestTimeout.txt
against master revision 71bb2de.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1822//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1822//console
This message is automatically generated.
> 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.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)
