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

TezQA commented on TEZ-3282:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12806829/TEZ-3282.01.txt
  against master revision bcf382e.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 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:red}-1 core tests{color}.  The patch failed these unit tests in :
                   org.apache.tez.dag.app.rm.TestContainerReuse

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/1760//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1760//console

This message is automatically generated.

> Set the Xms value when Tez computes the heap size for a container
> -----------------------------------------------------------------
>
>                 Key: TEZ-3282
>                 URL: https://issues.apache.org/jira/browse/TEZ-3282
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: TEZ-3282.01.txt
>
>
> Currently, we only set the Xmx value.
> Another useful change would be to change the calculation to not use the 
> fraction blindly. For large containers - .e.g 10GB - this ends up leaving 2G 
> of the container unused.
> Instead we can add another parameter which indicates the max amount of memory 
> to leave outside the heap. Maybe a separate jira for this.



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

Reply via email to