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

Bug 1279740

Summary: improve thread usage in VDSM requests
Product: [oVirt] vdsm Reporter: Oved Ourfali <oourfali>
Component: CoreAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.17.10CC: bugs, gklein, mgoldboi, pkliczew, pstehlik, pzhukov
Target Milestone: ovirt-3.6.1Keywords: CodeChange
Target Release: 4.17.11Flags: rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
oourfali: devel_ack+
pstehlik: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-16 12:24:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1269424    

Description Oved Ourfali 2015-11-10 07:50:51 UTC
Creating new thread for every request is not efficient.
We need to introduce usage an executor for request processing.

Comment 1 Pavel Stehlik 2015-11-10 10:19:42 UTC
QE you can also by check of opened threads.

Comment 2 Oved Ourfali 2015-11-24 07:02:03 UTC
Piotr - should this be on modified?

Comment 3 Piotr Kliczewski 2015-11-24 10:50:27 UTC
Yes. Changing it to modify.

Comment 4 Sandro Bonazzola 2015-11-24 16:43:55 UTC
Please set target release or I can't move the bug to ON_QA automatically.

Comment 5 Red Hat Bugzilla Rules Engine 2015-11-24 18:09:38 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 6 Jiri Belka 2015-12-03 13:38:54 UTC
codechange, no visible strange behaviour seen when using this vdsm version

Comment 7 Sandro Bonazzola 2015-12-16 12:24:17 UTC
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.