United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6975964 G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set
6975964 : G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set

Details
Type:
Enhancement
Submit Date:
2010-08-10
Status:
Closed
Updated Date:
2011-04-23
Project Name:
JDK
Resolved Date:
2011-04-23
Component:
hotspot
OS:
generic
Sub-Component:
gc
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
hs19
Fixed Versions:
hs19

Related Reports
Backport:
JDK-2197554 - G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set
Backport:
JDK-2198047 - G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set
Backport:
JDK-2199745 - G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set
Backport:
JDK-2197845 - G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set

Sub Tasks

Description
When an evacuation failure occurs in G1, G1 outputs "--" or "(evacuation failed)" in the GC log. Some users are worried when they read than something "fails" in the log. We should rephrase it.

Thanks to Jon Masamitsu for bringing this up.

Comments
PUBLIC COMMENTS

On this change I'll piggy-back a very small additional change which is to remove the printing of the duration of the mark closure when marking is on. I.e., this 

[GC pause (young)Mark closure took  5.72 ms.
, 0.07517200 secs]

will look like this after the change:

[GC pause (young), 0.07517200 secs]

The mark closure output was messing up the parsing of the logs.
2010-08-17 
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/b63010841f78
2010-08-17 
PUBLIC COMMENTS

Instead of evacuation failure we'll use the word "overflow". So, "evacuation failure" becomes "to-space overflow". Additionaly, when +G1PrintHeapRegions is set we currently print out "evacuation failed in heap region...". We'll change that to "overflow in heap region...".
2010-08-11 
EVALUATION

See Description.
2010-08-10


Hardware and Software, Engineered to Work Together