Bug 1575562
Summary: | Memory leak in ovirt-engine deployed as RHHI | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Mauro Oddi <moddi> | ||||
Component: | ovirt-engine | Assignee: | Sahina Bose <sabose> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | SATHEESARAN <sasundar> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.1.11 | CC: | lsurette, mgoldboi, mkalinin, moddi, mperina, Rhev-m-bugs, rnori, sabose, sasundar, srevivo, ykaul | ||||
Target Milestone: | ovirt-4.3.1 | Flags: | lsvaty:
testing_plan_complete-
|
||||
Target Release: | 4.3.0 | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-02-11 10:38:13 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Mauro Oddi
2018-05-07 10:17:44 UTC
Any logs? Ravi, any news? From the logs I see that in 8 hours time frame GlusterServersListVDSCommand and GlusterVolumesListVDSCommand is executed 9665 times each. Every three seconds there is an execution of the commands. Apart from the above issue I don't see anything else in the logs or the thread dump. It looks like there is an issue with Gluster integration. Created attachment 1443379 [details]
engine.log after ParOldGen gets to 99% (RHV 4.1.11) before engine restart
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. What's the next step here? (In reply to Yaniv Kaul from comment #56) > What's the next step here? We have not been able to reproduce the memory leak issue, and there has not been any further information from the customer. Mauro, can we close this bug? Mauro, any update? Should we continue to keep this bug open? Closing as we do not have enough data/ understanding of customer specific issue to proceed |