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

Hadoop QA commented on AMBARI-17818:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12819265/AMBARI-17818.2.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 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 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 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7953//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7953//console

This message is automatically generated.

> Tez & Hive: Memory management should use scaled down Xmx for sizing buffers
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-17818
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17818
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>            Reporter: Gopal V
>            Assignee: Gopal V
>         Attachments: AMBARI-17818.1.patch, AMBARI-17818.2.patch
>
>
> The defaults in Ambari assume 80% of the YARN container size is allocate to 
> the user heap (Xmx).
> On top of this particular restriction, the allocation blocks are divided into 
> Eden/Survivor/Tenured - a single allocation spanning 40% of the heap might 
> fail for tez runtime.io.sort.mb.
> Scale down the Tez sort size and map join by 0.8x to match Xmx.



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

Reply via email to