Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1064312 - Pool VMs are being pulled from template view in a very inefficient way
Pool VMs are being pulled from template view in a very inefficient way
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.3.0
Unspecified Unspecified
urgent Severity high
: ---
: 3.4.0
Assigned To: Liran Zelkha
Tareq Alayan
infra
: ZStream
Depends On:
Blocks: 1066392 rhev3.4beta 1142926
  Show dependency treegraph
 
Reported: 2014-02-12 07:00 EST by Tomas Dosek
Modified: 2016-02-10 14:13 EST (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, an inefficient query caused virtual machine pools pulled from template view to take a long time. This resulted in the query taking longer than expected to display results. Now, an updated query has fixed the problem. As a result, virtual machine pools are displayed more quickly.
Story Points: ---
Clone Of: 1061185
: 1066392 (view as bug list)
Environment:
Last Closed: 2014-06-09 11:03:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
talayan: needinfo-


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 24612 None None None Never
oVirt gerrit 24615 None None None Never
oVirt gerrit 24633 None None None Never
Red Hat Product Errata RHSA-2014:0506 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.4.0 update 2014-06-09 14:55:38 EDT

  None (edit)
Comment 1 Tomas Dosek 2014-02-12 07:02:44 EST
Same observation as with templates and events was found with pools. :(

SELECT * FROM (SELECT * FROM vm_pools_full_view WHERE ( vm_pool_id IN (SELECT vm_pools_full_view.vm_pool_id FROM  vm_pools_full_view  ))  ORDER BY vm_pool_name ASC ) as T1 OFFSET (1 -1) LIMIT 100
Comment 3 Liran Zelkha 2014-02-17 04:25:30 EST
Hi Tomas,

I can't understand what is the bug - is it from the vm_pools table or is it audit log table?
Comment 4 Tomas Dosek 2014-02-17 04:29:26 EST
Sorry for that I really should not have cloned the BZ from the previous one.

The inefficient query is:

SELECT * FROM (SELECT * FROM vm_pools_full_view WHERE ( vm_pool_id IN (SELECT vm_pools_full_view.vm_pool_id FROM  vm_pools_full_view  ))  ORDER BY vm_pool_name ASC ) as T1 OFFSET (1 -1) LIMIT 100

So that looks like vm_pools table/view.
Comment 5 Liran Zelkha 2014-02-18 02:09:21 EST
Hi Tomas,

Gerrit patch released, and will be available for 3.3.z. 
Note that the fix is validated for api call - http://localhost:8080/ovirt-engine/api/vmpools, without any parameters. This is the scenario you are testing, right?
Comment 7 Sandro Bonazzola 2014-02-19 07:01:59 EST
All patches merged.
Comment 8 Sandro Bonazzola 2014-02-19 07:05:01 EST
Maybe one patch need to be pushed to 3.4, please check if we're missing something in 3.4, otherwise please move to modified.
Comment 9 sefi litmanovich 2014-03-10 12:59:26 EDT
Just to make sure, this bug is an upstream bug and not a z-stream right?
Comment 10 Liran Zelkha 2014-03-10 15:28:15 EDT
Yes. It has a duplicate for downstream (1066392)
Comment 11 Tareq Alayan 2014-03-18 08:34:48 EDT
is this merged to rhevm-3.4.0-0.5.master ?
Comment 12 Liran Zelkha 2014-03-18 08:43:23 EDT
These are the 3.4 tags I'm familiar with - which one do you mean?

ovirt-engine-3.4.0_beta1
ovirt-engine-3.4.0_beta2
ovirt-engine-3.4.0_beta3
ovirt-engine-3.4.0_rc1
ovirt-engine-3.4.0_rc2
ovirt-engine-3.4.0_rc3
Comment 13 Tareq Alayan 2014-03-18 09:01:56 EDT
I want to verify that this merged into the downstream 3.4  ovirt-engine-3.4.0_av3 



How can i verify that?
Comment 14 Tareq Alayan 2014-03-18 09:10:39 EDT
the fix is there and verified.
Comment 15 errata-xmlrpc 2014-06-09 11:03:58 EDT
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.

http://rhn.redhat.com/errata/RHSA-2014-0506.html

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