| Summary: | [RFE] add support for recycling virt-who workers after reaching specified amount of memory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Martin Bacovsky <mbacovsk> | ||||
| Component: | virt-who | Assignee: | William Poteat <wpoteat> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Eko <hsun> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | --- | CC: | rjerrido, wpoteat, yuefliu | ||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||
| Target Release: | 8.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-06-05 08:33:35 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
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: