Project

General

Profile

Bug #2753

Specifying max_job limits for a single Frontend seems broken

Added by Burt Holzman over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Parag Mhashilkar
Category:
Factory
Target version:
Start date:
06/20/2012
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

From Jeff Dost:

--

Hello,

We encountered an urgent situation where we needed to reduce the limits of Running glideins for a single frontend while trying not to affect others. If I understand correctly this should be possible as follows in the max_job_frontends section.

<max_jobs held="1000" idle="4000" running="10000">
<default_max_jobs_frontend held="50" idle="100" running="5000"/>
<max_job_frontends>
<max_job_frontend name="CMS-CERN" held="50" idle="100" running="650" security_class="All"/>
</max_job_frontends>
</max_jobs>

Do I have the syntax correct? I don't see the max_job_frontend documented anywhere so I guessed it by looking at the source code. After setting this no new glideins ever submit to the entry and I see the following errors in the entry factory.*.info and err logs:

[2012-06-16T15:52:11-07:00 21817] WARNING: Error occurred while trying to find and do work.

Unfortunately nothing else is written to the debug log to know what may be the problem.

Can you please let us know whether I simply don't have this configured correctly or if it is a bug? This is occurring with glideinWMS v2_5_7.

Thanks,
Jeff


Subtasks

Bug #2757: Specifying glidein limits for different security classes for the same frontend is not possibleClosedParag Mhashilkar

History

#1 Updated by Krista Larson over 7 years ago

I think Jeff is using the wrong syntax. He needs to specify the security class name and not "all". But "all" is the default so we need to change this or add support to apply to all security classes for a frontend. Also, there was no good err logging - this could either be caught as part of the validation of the config (if we ever add this) or there could be a catch for errs when initializing the limits.

#2 Updated by Burt Holzman over 7 years ago

Ok. One step at a time -- let's correct first the documentation to indicate that this applies only to specific security classes, and then worry about
adding support for "All" later.

#3 Updated by Parag Mhashilkar over 7 years ago

I already talked to Jeff and Krista. Just so everyone knows, right now I have updated the docs and will try to see if this broken. We can discuss about the "All" based on what I find out.

#4 Updated by Parag Mhashilkar over 7 years ago

  • Status changed from Assigned to Feedback
  • Target version changed from v2_7_x to v2_6

v2+: commit:c590d4e
master: commit:5b9266e

#5 Updated by Parag Mhashilkar over 7 years ago

  • Status changed from Feedback to Resolved

#6 Updated by Parag Mhashilkar over 7 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF