concurrent mode failure during concurrent sweep phase

Kirk Pepperdine kirk at kodewerk.com
Wed Aug 15 12:01:53 UTC 2012


Hi all,

: 81092K->81092K(81856K), 0.3419045 secs]5274.145: [CMS5281.056: [CMS-concurrent-sweep: 11.066/12.602 secs]

In all of the GC logs I've got, this one doesn't show up very often. Now that I'm looking at it I'm asking myself... does it really make sense to declare a CMF when one is so close to the end of the CMS cycle? This really literally just small numbers of instructions away from the CMS-reset.... Wouldn't it make more sense to delay the ParNew that is hoisting survivors into CMS tenured vs triggering a full gc with it's (most likely longer) STW pause? Or is this a signal that the failure is most likely due to high fragmentation?

Regards,
Kirk


More information about the hotspot-gc-dev mailing list