Re: [HTCondor-devel] can anyone think of a use for this knob?

[Igor Sfiligoi <sfiligoi@xxxxxxxx>]

Hi Todd.

We use in glideinWMS... with the defaults being
NEGOTIATOR_MAX_TIME_PER_SUBMITTER=60
NEGOTIATOR_MAX_TIME_PER_PIESPIN=20

The idea is/was to limit the damage a single overloaded schedd can do,
without excessively penalizing a submitter.

Ideally, I would like to keep this knob around for a while, to simplify upgrades...
but if it is really a major thorn in the code, I guess we could live without it.

Cheers,
  Igor

On 03/20/2014 01:56 PM, Todd Tannenbaum wrote:
> I would like to get rid of the HTCondor knob
>    NEGOTIATOR_MAX_TIME_PER_PIESPIN
>
> I think perhaps the only reason this knob exists is because (at least at one point) the per submitter limit is/was only enforced on pie spin boundaries.
>
> If I were to fix the per user enforcement properly, do either of you have a problem if NEGOTIATOR_MAX_TIME_PER_PIESPIN went away?
>
> We would then be left with per user limit and a total negotiation cycle (across all spins) limit.  If I have time, I'd like to add a per schedd limit.
>
> Any issues/concerns with the above?
>
> thanks
> Todd