Bug 695057

Summary: [vdsm][scale] when ~150 vms are running on a host and restarting libvirtd, prepareForShutdown takes ~35 minutes.
Product: Red Hat Enterprise Linux 6 Reporter: David Naori <dnaori>
Component: vdsmAssignee: Igor Lvovsky <ilvovsky>
Status: CLOSED ERRATA QA Contact: David Naori <dnaori>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: abaron, bazulay, hateya, iheim, lpeer, mgoldboi, tdosek, ykaul
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.9-61 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:14:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
vdsm log none

Description David Naori 2011-04-10 09:28:39 UTC
Created attachment 491049 [details]
vdsm log

Description of problem:
when a host running 150 vms and connection to libvirtd is lost, prepareForShutdown takes ~35 minutes to complete.  

Thread-630::ERROR::2011-04-10 11:05:56,528::libvirtconnection::69::vds::(wrapper) connection to libvirt broken. taking vdsm down...

clientIFinit::INFO::2011-04-10 11:40:19,255::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: prepareVolume, Return response: {'status': {'message': 'OK', 'co
de': 0}}


MainThread::INFO::2011-04-10 11:40:26,254::vdsm::71::vds::(run) I am the actual vdsm 4.9-58

Version-Release number of selected component (if applicable):
vdsm-4.9-58.el6.x86_64
libvirt-0.8.7-16.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.run 150 vms
2.restart libvirtd

full vdsm log attached

Comment 2 Tomas Dosek 2011-05-04 07:42:02 UTC
Verified - vdsm-4.9-63.el6 - on large scale environment (1 quite powerful host - many vms) this bug no longer reproduces.

Comment 3 errata-xmlrpc 2011-12-06 07:14:09 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.

http://rhn.redhat.com/errata/RHEA-2011-1782.html