I have a cluster. Recently, it often happens "RESOURCE_MANAGER_GC_DURATION concerning". Observe the GC Collection Time case, each time it lasts for about 12s to 18s duration. JVM Heap size configuration situation 4GB, the overall usage of about 92%, in a high water situation. Please help to give suggestions. The clusters of following specifications: CDH version:5.7.0 Node info service HostName: P1 Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz Memory:256G cloudera-mgmt-HOSTMONITOR, cloudera-mgmt-EVENTSERVER, cloudera-mgmt-SERVICEMONITOR, cloudera-mgmt-ALERTPUBLISHER, cloudera-mgmt-ACITVITYMONITOR postgresql, hdfs-FAILOVERCONTROLLER, hdfs-NAMENODE, hbase-MASTER, yarn-RESOURCEMANAGER, yarn-NODEMANAGER zookeeper-ZOOKEEPER_SERVER HostName: Q1 Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz Memory:256G hdfs-FAILOVERCONTROLLER, hdfs-NAMENODE, hdfs-HTTPFS, hbase-MASTER, yarn-RESOURCEMANAGER, yarn-NODEMANAGER, oozie-OOZIE_SERVER zookeeper-ZOOKEEPER_SERVER HostName: R1 Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz Memory:512G hdfs-DATANODE, hdfs-JOURNALNODE, zookeeper-ZOOKEEPER_SERVER, hbase-REGION_SERVER, Hive-HIVE Metastore server Hive-HiveServer2 yarn-NODEMANAGER, Yarn-JobHistory Server spark_on_yarn-SPARK_HISTORY_SERVER HostName: S1 Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz Memory:512G hdfs-DATANODE, hdfs-JOURNALNODE, zookeeper-ZOOKEEPER_SERVER, hbase-REGION_SERVER, yarn-NODEMANAGER HostName: T1 Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz Memory:512G hdfs-DATANODE, hdfs-JOURNALNODE, zookeeper-ZOOKEEPER_SERVER, hbase-REGION_SERVER, yarn-NODEMANAGER
... View more
