When encountering FGC, HeapDumpBeforeFullGC/AfterFullGC are commonly enabled to help with troubleshooting.
In the current implementation, unlike HeapDumpOnOutOfMemoryError, which will only generate one dump, these two flags will generate dumps for every FGC, increasing the risk of disk full.
Although these two flags are manageable, disabling them timely in production may not be easy.
To enhance production-friendliness, it would be beneficial to have the ability to limit the number of dumps triggered by these two flags.
In the current implementation, unlike HeapDumpOnOutOfMemoryError, which will only generate one dump, these two flags will generate dumps for every FGC, increasing the risk of disk full.
Although these two flags are manageable, disabling them timely in production may not be easy.
To enhance production-friendliness, it would be beneficial to have the ability to limit the number of dumps triggered by these two flags.
- csr for
-
JDK-8321442 Limit the number of heap dumps triggered by HeapDumpBeforeFullGC/AfterFullGC
-
- Closed
-
- relates to
-
JDK-8322989 New test serviceability/HeapDump/FullGCHeapDumpLimitTest.java fails
-
- Resolved
-
