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

Hudson commented on AMBARI-11870:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #22 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/22/])
AMBARI-11870. HDP-2.3 'hive.tez.java.opts' should not contain Xmx and add 
additional JDK1.8 params - extra check (srimanth) (sgunturi: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ae9562aa25107b2d3a56591490d49f4aa311daf8)
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py


> HDP-2.3 'hive.tez.java.opts' should not contain Xmx and add additional JDK1.8 
> params
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11870
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11870
>             Project: Ambari
>          Issue Type: Bug
>          Components: contrib
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11870.patch, AMBARI-11870_2.patch
>
>
> {{hive.tez.java.opts}} for HDP-2.3 should not contain the Xmx JVM parameter. 
> The reason for this is:
> {noformat}
> Tez does it based on the allocated container (i.e if you use a 1.5Gig 
> container.size and YARN returns a 4Gig one, Tez should use a 0.8*4096).
> https://github.com/apache/tez/blob/master/tez-api/src/main/java/org/apache/tez/client/TezClientUtils.java#L920
> This would work much better if you removed the whole Xmx parameter from the 
> config in hive-site.xml.
> {noformat}
> Also, for JDK8 the preferred GC isn't {{-XX:+UseParallelGC}} it is 
> {{-XX:+UseG1GC -XX:+ResizeTLAB}} while retaining all the other java 
> parameters. In some JDK7 versions, the G1GC occasionally segfaults, so the 
> choice of those two are based on whether the install is on JDK8 or not.



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

Reply via email to