[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] condor_status -total, Preempting
- Date: Mon, 27 Jan 2014 16:53:43 +0100
- From: Pek Daniel <pekdaniel@xxxxxxxxx>
- Subject: Re: [HTCondor-users] condor_status -total, Preempting
Some lines from the StartLog:
01/27/14 16:45:42 slot22: Request accepted.
01/27/14 16:45:42 slot22: Remote owner is xxx
01/27/14 16:45:42 slot22: State change: claiming protocol successful
01/27/14 16:45:42 slot22: Changing state: Unclaimed -> Claimed
01/27/14 16:45:46 slot22: Got activate_claim request from shadow
01/27/14 16:45:46 slot22: Remote job ID is 3920.25
01/27/14 16:45:46 slot22: Got universe "VANILLA" (5) from request classad
01/27/14 16:45:47 slot22: State change: claim-activation protocol successful
01/27/14 16:45:47 slot22: Changing activity: Idle -> Busy
01/27/14 16:45:55 slot22: Preempting claim has correct ClaimId.
01/27/14 16:45:55 slot22: New claim has sufficient rank, preempting
01/27/14 16:45:55 slot22: State change: preempting claim based on user priority
01/27/14 16:45:55 slot22: State change: claim retirement ended/expired
01/27/14 16:45:55 slot22: Changing state and activity: Claimed/Busy ->
2014/1/27 Pek Daniel <pekdaniel@xxxxxxxxx>:
> I tried my best to turn off preemption completely:
> PREEMPT = FALSE
> SUSPEND = FALSE
> KILL = FALSE
> PREEMPTION_REQUIREMENTS = FALSE
> NEGOTIATOR_CONSIDER_PREEMPTION = FALSE
> RANK = 0
> But sometimes during negotiation, I still can see non-zero value in
> the Preempting column of the output of condor_status -total.
> According to the docs:
> ``Preempting'': A Condor job is being preempted (possibly via
> checkpointing) in order to clear the machine for either a higher
> priority job or because the machine owner wants the machine back.
> Regarding that I have only one single user and completely identical
> jobs, I don't think the preemption would happen because of a higher
> priority job. Any idea why is this?