Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1098791

Summary: Reduce blocking operations as part of hosts & VMs monitoring cycles
Product: Red Hat Enterprise Virtualization Manager Reporter: Arik <ahadas>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: agkesos, gklein, iheim, lpeer, mavital, michal.skrivanek, mkalinin, rbalakri, Rhev-m-bugs, scohen, yeylon
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: ovirt-engine-3.5.0_beta Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1108675 1110140 (view as bug list) Environment:
Last Closed: 2015-02-11 18:02:12 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:
Bug Depends On:    
Bug Blocks: 1081962, 1108675, 1110140, 1142923, 1156165    

Description Arik 2014-05-18 15:27:15 UTC
Description of problem:
While investigating [1], we noticed that the handling of VMs that went down is being processed synchronously as part of each iteration of VdsUpdateRunTimeInfo. When we had to handle 50 VMs that went down on the same host at the same time, it caused the iteration to take ~9 minutes.
We should extract the code this code that handles VMs that went down to be executed as part of different thread/job as well as other similar synchronous operation that are made within the VURTI thread.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Run 50 stateless VMs on one host
2. Shutdown all VMs at the same time
3.

Actual results:
iteration of VURTI can take more than 9 minutes

Expected results:
the iteration of VURTI end as soon as possible, and the long operations that block it should be executed in different thread.

Additional info:
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1085760

Comment 4 Ilanit Stein 2014-08-12 06:42:46 UTC
Verified on ovirt-engine 3.5-rc1.

50 VMs (in a Vmpool), 512 MB memory, 1G disk, no OS installed.
All 50 VMs run on the same host.
Power off all 50 VMs took ~ 0.5 minute.

Comment 5 Arik 2014-08-15 19:30:06 UTC
*** Bug 1099846 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2015-02-11 18:02:12 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/RHSA-2015-0158.html