Bug 1394050 - [RFE] add support for recycling virt-who workers after reaching specified amount of memory
Summary: [RFE] add support for recycling virt-who workers after reaching specified amo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-who
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: William Poteat
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 22:04 UTC by Martin Bacovsky
Modified: 2020-06-05 08:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-05 08:33:35 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)
Virt-who memory usage sample (16.78 KB, image/png)
2016-11-10 22:04 UTC, Martin Bacovsky
no flags Details

Description Martin 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:

Comment 2 Rich Jerrido 2020-06-05 08:33:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.