Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

GC Duration warnings on CDH 5.5.1 cluster

avatar
Expert Contributor

Hi,

 

We recently started getting the GC warnings on our Yarn and all nodes of Production cluster frequently, so want to avoid this warnings. Please someone can help us to resolve this issue as soon as possible.

 

Following is the warning:

 

Test of whether this role spends too much time in garbage collection. Concerning

Average time spent in garbage collection was 19.8 second(s) (32.97%) per minute over the previous 5 minute(s). Warning threshold: 30.00%.
1 ACCEPTED SOLUTION

avatar
Rising Star

you will need to append "

 -Xms512m -Xmx1024m -XX:PermSize=216m -XX:MaxPermSize=512m

"

to the property  Java Configuration Options for Node Manager, and then restart Node Managers. You'll want to change  the numbers for -Xmx and -XX:MaxPermSize to values bigger than what you currently have for Node Manager. Please try to do this in a test enviroment first as this may impact on your production cluster.

View solution in original post

13 REPLIES 13

avatar
Expert Contributor

Can you please be more specific to this, like how to find out the current setting for following:

 

-Xms512m -Xmx1024m -XX:PermSize=216m -XX:MaxPermSize=512m

avatar
Rising Star

avatar
Expert Contributor

Ok we applied the following configuration as recommended on our Dev Cluster and are seeing no issues.

 

 

property: Java Configuration Options for NodeManager:

 

-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=70 -XX:+CMSParallelRemarkEnabled -Xms512m -Xmx2048m -XX:PermSize=216m -XX:MaxPermSize=512m

 

But the point to note is GC Duration warnings had never happened on this cluster, it happened on our Production cluster. 

 

So shall we go ahead and make changes on Production cluster or there are any other things we have to consider ?

 

Please any suggestions

avatar
Rising Star

Is it possible for you to try the same settings in your production cluster? If your dev cluster is very close to production server in terms of workload, then I'd guess this will alleviate gc pause in your production cluster as well.