Description of problem: Because the new generational GC trades additional memory utilization for less CPU utilization, the worker is consuming more than the default configuration of 250MiB much of the time. This causes the worker to be terminated and restarted. Version-Release number of selected component (if applicable): 5.5.2 How reproducible: More than 50% of the time under moderate load. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=230fc0f5fa7059bf7a382bd4c153cac44acd9f36 commit 230fc0f5fa7059bf7a382bd4c153cac44acd9f36 Author: Dennis Metzger <dmetzger> AuthorDate: Mon Feb 29 20:16:46 2016 -0500 Commit: Dennis Metzger <dmetzger> CommitDate: Mon Feb 29 20:16:46 2016 -0500 Increasing the schedule_worker memory threshold to 300Mib as it now exceeds the current 250MiB default more the half the time. The additional memory utilization is the result of the generation GC trading memory for CPU utilization. https://bugzilla.redhat.com/show_bug.cgi?id=1313122 config/vmdb.tmpl.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=fe3d85a6f8e798ab38619066d3bc647a7bdd8e8e commit fe3d85a6f8e798ab38619066d3bc647a7bdd8e8e Merge: f6db2d6 230fc0f Author: Joe Rafaniello <jrafanie> AuthorDate: Tue Mar 1 10:23:54 2016 -0500 Commit: Joe Rafaniello <jrafanie> CommitDate: Tue Mar 1 10:23:54 2016 -0500 Merge branch '5.5.z' into '5.5.z' Increasing the schedule_worker memory threshold to 300Mib Increasing the default memory threshold to 300MiB because the schedule_worker routinely exceeds the current 250MiB as a result of the generational GC trading more memory https://bugzilla.redhat.com/show_bug.cgi?id=1313122 See merge request !827 config/vmdb.tmpl.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Merge Request #827
Verified the local appliance setting is correct per the code check-in above. Moving to verified on 5.6.0.1 Beta 2 using 10.16.7.174
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348