[
https://issues.apache.org/jira/browse/AMBARI-18006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405993#comment-15405993
]
Hadoop QA commented on AMBARI-18006:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12821842/AMBARI-18006.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8269//console
This message is automatically generated.
> Tune HDFS opts parameters to trigger GC more predicitably
> ---------------------------------------------------------
>
> Key: AMBARI-18006
> URL: https://issues.apache.org/jira/browse/AMBARI-18006
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18006.patch
>
>
> DN Heap usage alert is set to 80% warning and 90% critical. This alert is
> causing a lot of alerts to be fired off and needs to be tuned.
> One thing we need to make sure is that DN gc is happening. I am not sure at
> what % of heap usage will the gc be fired but we need to make sure our alerts
> are for a % higher than that as when i manually ran a GC the heap usage went
> below the threshold.
> Based on discussions with hdfs dev's it was determined we should be adding the
> following
>
>
>
> XX:+UseCMSInitiatingOccupancyOnly and
> -XX:CMSInitiatingOccupancyFraction=<percent>
>
> to the namenode and datanode opts. Based on this setting hopefully we can also
> determine what % to set the alerts to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
