[
https://issues.apache.org/jira/browse/AMBARI-16691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-16691:
-----------------------------------
Status: Patch Available (was: In Progress)
> 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
>
> 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)
