This config parameter should no longer be relevant, as the amazon_gahp no longer creates worker processes.

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.

I was thinking the gahp was still single-threaded for some reason. I've pushed a fix to the 7.1 branch.

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.

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