Bug 451799 - upfront construction of ec2 KeyPairs is time consuming
upfront construction of ec2 KeyPairs is time consuming
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
beta
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthew Farrellee
Kim van der Riet
:
Depends On:
Blocks: 463363
  Show dependency treegraph
 
Reported: 2008-06-17 09:52 EDT by Matthew Farrellee
Modified: 2008-10-07 14:42 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-07 14:42:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matthew Farrellee 2008-06-17 09:52:41 EDT
The gridmanager will construct KeyPairs for all outstanding EC2 jobs upfront.
This can lead to a delay in starting jobs when there are many (10K for instance)
EC2 jobs queued.
Comment 1 Jaime Frey 2008-09-10 16:12:40 EDT
This is fixed in the V7_1 branch. The construction of keypairs is now restricted by the gridmanager's submission throttles.
Comment 2 Matthew Farrellee 2008-09-11 00:24:15 EDT
This is tested by submitting a set of 100 jobs (any number greater than GRIDMANAGER_MAX_SUBMITTED_JOBS_PER_RESOURCE will work), and after some begin to run check the set of created keypairs with ec2-describe-keypairs. If there are more keypairs than running jobs this issue still exists.
Comment 7 errata-xmlrpc 2008-10-07 14:42:25 EDT
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

Note You need to log in before you can comment on or make changes to this bug.