Bug 1223053 - [scale] Excessive cpu usage in FileStorageDomain.getAllVolumes
Summary: [scale] Excessive cpu usage in FileStorageDomain.getAllVolumes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 3.5.4
Assignee: Nir Soffer
QA Contact: Eldad Marciano
URL:
Whiteboard: storage
Depends On: 1179950
Blocks: 1177634
TreeView+ depends on / blocked
 
Reported: 2015-05-19 17:19 UTC by Nir Soffer
Modified: 2016-02-10 18:15 UTC (History)
12 users (show)

Fixed In Version: vdsm-4.16.21-1.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of: 1179950
Environment:
Last Closed: 2015-09-03 18:12:44 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
ylavi: Triaged+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1729 0 normal SHIPPED_LIVE vdsm 3.5.4 - bug fix and enhancement update 2015-09-03 22:11:47 UTC
oVirt gerrit 36593 0 None None None Never
oVirt gerrit 41127 0 ovirt-3.5 MERGED fileSD: Optimize getAllVolumes on file storage Never

Comment 1 Nir Soffer 2015-05-19 17:21:29 UTC 
Clone this bug since we are using the fix on master for few month, and I think this fix is safe.
Comment 2 Eldad Marciano 2015-07-22 07:21:51 UTC 
verified on top of vt16.2

by profiling vdsm looks like getAllVolumes doesn't listed at the longest chart anymore.
Comment 3 Eldad Marciano 2015-07-22 07:22:05 UTC 
verified on top of vt16.2

by profiling vdsm looks like getAllVolumes doesn't listed at the longest chart anymore.
Comment 5 errata-xmlrpc 2015-09-03 18:12:44 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-1729.html
Note You need to log in before you can comment on or make changes to this bug.