What do the multiple reported times mean when a Full GC occurs as the result of a concurrent mode failure?

Solution Verified - Updated -

Issue

  • How to interpret concurrent mode failure timestamps in Garbage Collection (GC) logs

  • In the following log snippet, 1.264, is the CPU, while 72740 is what is classified as wall time', but at the end of the gc log entry, have another two elements about cpu time, that would be user and sys, do they have any relation with '1.264' I can find from the gc log entry(so does '72740.163' and '72729.22')? And now I have '1.264/72740.163' and 'Times: user=3.86 sys=0.00, real=2.86 secs' two block about, which of the block is more meaningful to me?

    8477579.922: [Full GC 8477579.922: [CMS8477580.934: [CMS-concurrent-mark: 1.264/72740.163 secs] [Times: user=393.00 sys=43.13, real=72729.22 secs]  (concurrent mode failure): 3075148K->594654K(3145728K), 2.8537840 secs] 4018892K->594654K(4089472K), [CMS Perm : 160302K->159744K(393216K)] icms_dc=22 , 2.8540090 secs] [Times: user=3.86 sys=0.00, real=2.86 secs]
    
  • Need more information to understand / interpret the GC logs where concurrent mode failure is concerned

Environment

  • Java
    • Concurrent Mark Sweep (CMS) collector GC logs

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content