Red Hat Bugzilla – Bug 1296192
Reduce Memory usage of MiqScheduleWorker or raise memory threshold
Last modified: 2017-12-05 10:16:31 EST
Created attachment 1112200 [details]
220.127.116.11 MiqScheduleWorker Memory Usage
Description of problem:
18.104.22.168 experiences recycling (exiting and restarting) the MiqScheduleWorker in many of the memory baseline tests. The threshold is set to 250.megabytes in the advanced configuration. 22.214.171.124-2 and 126.96.36.199 also has the MiqScheduleWorker memory threshold set to 250.megabytes however it does not recycle in any of the same scenarios.
This has been found in two memory baselining scenarios: Capacity and Utilization and Provisioning.
Reviewing historical for 188.8.131.52-2 and 184.108.40.206, the MiqScheduleWorker does not recycle in any of the same scenarios suggesting the additional memory growth was recently introduced. The memory usage does increase between 220.127.116.11 to 18.104.22.168-2 as expected (Move to Ruby 2.2) however not enough to come close to the memory threshold.
Version-Release number of selected component (if applicable):
~ >50% of the time (7 out of 13 tests showed this failure)
Steps to Reproduce:
Attaching Memory graphs of the MiqScheduleWorker during Capacity and Utilization memory baselining showing the following versions in the same scenario:
Created attachment 1112201 [details]
22.214.171.124-2 MiqScheduleWorker Memory Usage
Created attachment 1112202 [details]
126.96.36.199 MiqScheduleWorker Memory Usage
Created attachment 1112207 [details]
evm.log output from pid 8220 (MiqScheduleWorker)
Reviewing the CSV output of memory usage, the growth spurt in (rss, pss, uss) memory right before the worker exits starts between 16:36:57 and 16:37:07:
2016-01-05 16:36:37.221739 208.42578125
2016-01-05 16:36:47.231512 208.4921875
2016-01-05 16:36:57.241401 208.5
2016-01-05 16:37:07.251246 219.359375
2016-01-05 16:37:17.261163 230.15234375
2016-01-05 16:37:27.266662 238.265625
2016-01-05 16:37:37.277017 245.796875
2016-01-05 16:37:47.286422 252.53125
2016-01-05 16:37:57.293079 252.53125
*** Bug 1314113 has been marked as a duplicate of this bug. ***
188.8.131.52 has a limit of 300MiB for the MiqScheduleWorker and I have not seen this issue occur again on this build.
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.