Description of problem: The throttles to control submission to grid resources via the condor_gridmanager apply to all resources. GRIDMANAGER_MAX_PENDING_SUBMITS_PER_RESOURCE GRIDMANAGER_MAX_SUBMITTED_JOBS_PER_RESOURCE It would be desirable to have grid resource specific throttles. For instance, by default EC2 will not let you run more than 20 instances. So, setting MAX_SUBMITTED = 20 is critical, but other grid resources may allow for more than 20 submissions. Version-Release number of selected component (if applicable): condor 7.0.1-6
Setting these limits differently per grid-type is clearly necessary. We also have a request to set them differently per resource within a grid-type. I want to think about how to represent both in the Condor config file. How we represent the later may affect how we represent the former.
Fixed upstream... author Jaime Frey <...> commit 60883ab59c1398d2d7c2bc4c489050523f0585d3 Allow gridmanager resource limits to be set per-gridtype Added config parameters GRIDMANAGER_MAX_SUBMITTED_JOBS_PER_RESOURCE_<gridtype> and GRIDMANAGER_MAX_PENDING_SUBMITS_PER_RESOURCE_<gridtype>, which let you set these limits on a per-gridtype basis. The parameter names without a gridtype still work and are used if the gridtype-specific versions are absent for a given type.
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/RHBA-2009-0036.html