Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMartin Bacovsky
2016-11-10 22:04:39 UTC
Created attachment 1219560[details]
Virt-who memory usage sample
Description of problem:
On the attached graph we can see virt-who workers allocating big amount of memory due to some error or memory leak slowly leading to OOM-kill. Python processes tend to not returning allocated memory to the system even when the memory was freed. I would be great if virt-who workers can be automatically restarted after certain number of cycles or preferably after reaching some amount of allocated memory.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
The workers run indefinitely until the service is restarted
Expected results:
The workers are being recycled after reaching configurable limit.
Additional info:
Thank you for your interest. We have evaluated this request, and
while we recognize that it is a valid request, we do not expect this to be
implemented in the product in the foreseeable future. This is due to other
priorities for the product, and not a reflection on the request itself. We are
therefore closing this out as WONTFIX. If you have any concerns about this,
please do not reopen. Instead, feel free to contact Red Hat Technical Support.
Thank you.
Created attachment 1219560 [details] Virt-who memory usage sample Description of problem: On the attached graph we can see virt-who workers allocating big amount of memory due to some error or memory leak slowly leading to OOM-kill. Python processes tend to not returning allocated memory to the system even when the memory was freed. I would be great if virt-who workers can be automatically restarted after certain number of cycles or preferably after reaching some amount of allocated memory. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: The workers run indefinitely until the service is restarted Expected results: The workers are being recycled after reaching configurable limit. Additional info: