CM Server 5.2 hangs due to "Detected pause in JVM or host machine

[#1]

I found that CM server 5.2 hangs intermittently(sometimes it hangs within a week, sometimes hangs after running for two weeks):

# service cloudera-scm-server status
cloudera-scm-server dead but pid file exists

And the last few lines of cloudera-scm-server.log shows:

2015-02-01 03:11:49,047 INFO JvmPauseMonitor:com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 2901ms: GC pool 'ParNew' had collection(s): count=1 time=21ms, GC pool 'ConcurrentMarkSweep' had collection(s): count=2 time=3020ms
2015-02-01 03:11:49,060 INFO JvmPauseMonitor:com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 2914ms: GC pool 'ParNew' had collection(s): count=1 time=21ms, GC pool 'ConcurrentMarkSweep' had collection(s): count=2 time=3020ms
2015-02-01 03:11:54,106 INFO JvmPauseMonitor:com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 4546ms: no GCs detected.
2015-02-01 03:11:54,107 INFO JvmPauseMonitor:com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 4558ms: no GCs detected.

How can I fix this problem? Thx!

[#2]

iam having the same issue please fix it.

[#3]

Please configure more heap memory for the Cloudera Mangager process, follow instructions as shown in Increasing Max Heap Size | Cloudera Manager Service Control Manager

Please note those messages which state "no GCs detected" indicate the host is overloaded cpu wise.

[#4]

Hi @nkp,

What is your Cloudera Manager version?

To follow up with gziglgldrum's post, in case you can not access the article, here are some details copied from there:

To configure the maximum heap size of the SCM process, please do:

1) Edit the CMF_JAVA_OPTS property in the /etc/default/cloudera-scm-server file.
2) Alter last line of the file:
export CMF_JAVA_OPTS="-Xmx2G -XX:MaxPermSize=256m ..."
3) To configure more heap memory to Cloudera Manager, please change -Xmx2G to bigger value.

For example, -Xmx4G.

Note:  -Xmx2G option specifies 2 GB of RAM.
4) Restart Cloudera Manager by running below command:
sudo service cloudera-scm-server restart

You may also want to read this documentation to find out what is the recommended heap size for your Cloudera Manager:

https://www.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_hardware_requirements.ht...

Thanks and hope this helps,

Li