Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1060692

Summary:	ovirt-engine-backend [scalability]: Deadlock occurred during mass startup of VMs.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine	Assignee:	Omer Frenkel <ofrenkel>
Status:	CLOSED ERRATA	QA Contact:	Yuri Obshansky <yobshans>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	acathrow, adahms, bazulay, eedri, gklein, iheim, jkt, jturner, lpeer, michal.skrivanek, ofrenkel, ohochman, pstehlik, rgolan, Rhev-m-bugs, srevivo, yeylon, zdover
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	3.3.2
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, starting a large number of virtual machines at the same time could result in a deadlock, which would cause the action to fail. Now, the logic applied to starting virtual machines has been revised, improving performance by reducing database access, requiring fewer locks, and avoiding deadlocks.	Story Points:	---
Clone Of:	891316	Environment:
Last Closed:	2014-04-09 17:53:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	891316
Bug Blocks:

Comment 2 Barak 2014-02-03 12:03:36 UTC

Code was merged to 3.3.0 , moved to zstream for testing

Comment 3 Yuri Obshansky 2014-03-24 09:51:56 UTC

Bug verified 
Successfully started 100 VMs simultaneously on single host 
using JMeter and REST API
No exceptions through in log files: engine.log and console.log

Environment:
*************
rhevm 3.3.2-0.49.el6ev
vdsm-4.13.2-0.6.el6ev (on hosts) 
libvirt-0.10.2-29.el6_5.5 (on hosts)

Comment 4 Zac Dover 2014-04-03 02:26:35 UTC

This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 5 Omer Frenkel 2014-04-03 14:46:56 UTC

This bug was part of rhevm3.3, it is open just for testing purpose, is there a need for doc text?

Comment 6 Zac Dover 2014-04-08 05:13:52 UTC

If this is merely a testing bug, I will not write doc text for it.

Thanks,

Zac

Comment 8 errata-xmlrpc 2014-04-09 17:53:20 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/RHBA-2014-0384.html