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

Bug 451069

Summary: gSOAP amazon-gahp needs max to worker pool
Product: Red Hat Enterprise MRG Reporter: Matthew Farrellee <matt>
Component: gridAssignee: Matthew Farrellee <matt>
Status: CLOSED ERRATA QA Contact: Kim van der Riet <kim.vdriet>
Severity: high Docs Contact:
Priority: high    
Version: betaCC: jfrey, jneedle
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-07 18:42:18 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:    
Bug Blocks: 463362    

Description Matthew Farrellee 2008-06-12 17:03:13 UTC
config option AMAZON_GAHP_WORKER_MAX_NUM must be honored

Comment 1 Jaime Frey 2008-09-10 19:45:27 UTC
This config parameter should no longer be relevant, as the amazon_gahp no longer creates worker processes.

Comment 2 Matthew Farrellee 2008-09-11 03:57:36 UTC
The amazon_gahp takes -w <min # workers> and -m <max # workers>. A worker is no longer a separate process, but a separate pthread. The amazonjob.C param()s for and passes the AMAZON_GAHP_WORKER_MIN_NUM but does not do the same for the ..._MAX_NUM, leaving the max number of threads created unbounded.

Comment 3 Jaime Frey 2008-09-11 15:18:11 UTC
I was thinking the gahp was still single-threaded for some reason. I've pushed a fix to the 7.1 branch.

Comment 4 Matthew Farrellee 2008-09-11 15:52:32 UTC
This is tested by specifying AMAZON_GAHP_WORKER_MAX_NUM to some small value, say 2, submitting a number of jobs, say >> 2 , and verifying that the amazon-gahp does not create more than two threads at a time. Verification can be done by looking at the amazon-gahp process in the OS, or by looking at the amazon-gahp's log file to verify it only ever creates 2 threads.

Comment 7 errata-xmlrpc 2008-10-07 18:42:18 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2008-0911.html