JDK-8278285 : G1: Distinguish logging between the real evac failure and region pinning
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 21
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2021-12-06
  • Updated: 2024-02-23
  • Resolved: 2024-02-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8318706 - Implement JEP 423: Region Pinning for G1
Relates :  
JDK-8278286 - G1: Add an additional logging category such as "gc+evacfail" to switch on the most detailed statistics
Relates :  
JDK-8278287 - G1: Extend the gc+heap=debug messages to also show the number of failed regions of that category
Relates :  
JDK-8278282 - G1: Log basic statistics for evacuation failure
Relates :  
JDK-8278284 - G1: Log per region statistics of evacuation failure
Relates :  
JDK-8278283 - G1: Log further detailed statistics of evacuation failure
Description
It's helpful to distinguish between the real evac failure and region pinning when logging evacuation failure processing.


This is one of the follow-up tasks discussed at :
 - https://github.com/openjdk/jdk/pull/6627#pullrequestreview-821445879, and
 - https://github.com/openjdk/jdk/pull/6627#issuecomment-985478359
Comments
JDK-8318706 added that kind of logging: the evacuation failure tag has been augmented with one or both of "Allocation" and "Pinned", where the latter indicates that the evacuation failure has been caused due to object pinning
23-02-2024