-
Suggestion
-
Resolution: Fixed
Problem Definition
If you use the Garbage-First (G1) garbage collector, we recommend configuring your JVM parameters to avoid the risk of explicit STW (stop the world) GC, which causes Jira to become unavailable while the garbage collection cycle runs.
See Health Check: Explicit Garbage Collection for more details
Suggested Solution
Add '-XX:+ExplicitGCInvokesConcurrent' by default to Jira.
- It will be used by G1GC and CMS.
- It will be ignored by ParallelGC since there is no Concurrent phase for OldGen.
Context:
Other causes than Allocation Failure for a Full GC typically indicate that either the application or some external tool causes a full heap collection. If the cause is System.gc(), and there is no way to modify the application sources, the effect of Full GCs can be mitigated by using -XX:+ExplicitGCInvokesConcurrent
Workaround
None
- is related to
-
JRASERVER-70459 As a Jira admin, I want to have an easier way to set the flag -XX:+UseG1GC when using Java 11+
- Closed
- mentioned in
-
Page Loading...
- relates to
-
HL-1349 Loading...