ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16691) Atlas Integration : Extend Ambari with settings for Atlas environment configuration
Date Thu, 07 Jul 2016 17:16:11 GMT

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

Hadoop QA commented on AMBARI-16691:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12816640/AMBARI-16691.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 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 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/7729//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7729//console

This message is automatically generated.

> Atlas Integration : Extend Ambari with settings for Atlas environment configuration
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-16691
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16691
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>         Attachments: AMBARI-16691.patch
>
>
> In ATLAS-616, we uncovered problems with Atlas web service when testing queries at scale.
The investigation revealed a fix possible with tuning some GC parameters. ATLAS-616 suggests
the GC values in documentation.
> Default these settings in Ambari.
> The values we have recommended are all to be set in {{atlas-env.sh}} config file. They
are:
> Common for all JDKs:
> {code}
> #export ATLAS_SERVER_OPTS="-server -XX:SoftRefLRUPolicyMSPerMB=0 -XX:+CMSClassUnloadingEnabled
-XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+PrintTenuringDistribution -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=dumps/atlas_server.hprof -Xloggc:logs/gc-worker.log -verbose:gc -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1m -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintGCTimeStamps"
> {code}
> For JDK7:
> {code}
> #export ATLAS_SERVER_HEAP="-Xms15360m -Xmx15360m -XX:MaxNewSize=3072m -XX:PermSize=100M
-XX:MaxPermSize=512m"
> {code}
> For JDK8:
> {code}
> #export ATLAS_SERVER_HEAP="-Xms15360m -Xmx15360m -XX:MaxNewSize=5120m -XX:MetaspaceSize=100M
-XX:MaxMetaspaceSize=512m"
> {code}



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

Mime
View raw message