[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] drawbacks of NEGOTIATOR_INFORM_STARTD = False
- Date: Thu, 30 Jan 2014 10:56:39 -0600
- From: Greg Thain <gthain@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] drawbacks of NEGOTIATOR_INFORM_STARTD = False
On 01/30/2014 10:35 AM, Todd Tannenbaum wrote:
On 1/30/2014 2:11 AM, Pek Daniel wrote:
Is there any drawback of setting NEGOTIATOR_INFORM_STARTD to False?
One downside is if, for whatever reason, it takes the schedd a while
to get around to claiming a startd given to it by the negotiator.
E.g. maybe the submit machine is very busy, or maybe the schedd is
given a very large number of machines to claim all at once, etc. In
this case, you run the risk of the negotiator matching a startd to
scheddA, and then matching it again to scheddB in a subsequent
negotiation cycle because the startd will stay in Unclaimed state. If
NEGOTIATOR_INFORM_STARTD is True (the default), the startd will go to
Matched state and thus the negotiator will not give it away again.
Note that the first schedd to use the claim on the startd will "win",
and the subsequent use of that same claim be rejected by the startd as
invalid, forcing the second schedd to go to the negotiator to get new