ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18936) DataNode JVM heap settings should include CMSInitiatingOccupancy
Date Fri, 02 Dec 2016 21:59:58 GMT


Hudson commented on AMBARI-18936:

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #445 (See [])
AMBARI-18936. DataNode JVM heap settings should include (smohanty: [])
* (add) ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml

> DataNode JVM heap settings should include CMSInitiatingOccupancy
> ----------------------------------------------------------------
>                 Key: AMBARI-18936
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>    Affects Versions: 2.2.2
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>             Fix For: 2.5.0
>         Attachments: AMBARI-18936.02.patch
> This is a followup to AMBARI-18694 to fix remaining stack versions:
> ___________________________
> As HDFS-11047 reported, DirectoryScanner does scan by deep copying FinalizedReplica.
In a deployment with 500,000+ blocks, we've seen the DN heap usage being accumulated to high
peaks very quickly. Deep copies of FinalizedReplica will make DN heap usage even worse if
directory scans are scheduled more frequently. 
> Another factor is that huge number of ScanInfo instances corresponding to HDFS blocks
are lingering in garbage to eat many heap memories until a full GC takes place.
> This proposes adding JVM settings to force GC more frequently to release DataNode heap
consumed as a result of two aforementioned reasons, i.e. add the options to HADOOP_DATANODE_OPTS
> {noformat}
> -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly -XX:ConcGCThreads=8
> {noformat}

This message was sent by Atlassian JIRA

View raw message