Re: [HTCondor-users] Ticket #6463: Change IS_OWNER default to False

[Zach Miller <zmiller@xxxxxxxxxxx>]

Hi Greg,

 

As you suggested, manually setting IS_OWNER to the previous default value should fix that issue and if that's all you care about fixing, that's probably easiest.

 

However, you might want to consider instead setting "use POLICY:Desktop".  This is a "metaknob" which is a shortcut for setting a whole bunch of things.  Here's exactly what that does:

 

use POLICY:Desktop is

        WANT_SUSPEND=($(SmallJob) || $(KeyboardNotBusy) || $(IsVanilla) ) && ( $(SUSPEND))

        WANT_VACATE=$(ActivationTimer) > 600 || $(IsVanilla)

        SUSPEND=($(KeyboardBusy) || ( (CpuBusyTime > 120) && $(ActivationTimer) > 90))

        CONTINUE=($(CPUIdle) && ($(ActivityTimer) > 10) && (KeyboardIdle > $(ContinueIdleTime)))

        PREEMPT=(((Activity == "Suspended") && ($(ActivityTimer) > $(MaxSuspendTime))) || (SUSPEND && (WANT_SUSPEND == False)))

        START=((KeyboardIdle > $(StartIdleTime)) && ( $(CPUIdle) || (State != "Unclaimed" && State != "Owner")) )

        KILL=False

        MaxJobRetirementTime=0

        CLAIM_WORKLIFE=

        SLOTS_CONNECTED_TO_KEYBOARD=$(NUM_CPUS)

        IS_OWNER=(START =?= False)

 

 

As you can see, the list line restores that particular behaviour.  You may want some of the other behaviors listed there, or maybe you are also setting those manually elsewhere in your config.  The idea is that if you set the metaknob instead, and down the line we figure out ways to improve "a good policy for a desktop", you won't have to change your config and it will pick up the new meaning and settings of the metaknob.

 

 

Cheers,

-zach

 

 

-----Original Message-----
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Hitchen, Greg (IM&T, Kensington WA) <Greg.Hitchen@xxxxxxxx>
Date: Friday, February 19, 2021 at 2:03 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Ticket #6463: Change IS_OWNER default to False

I think we’ve just been bitten by this change when upgrading from 8.6.12 to 8.8.12

 

Looking through the 8.7 development series changelog shows:

 

Version 8.7.6

Release Notes:

    HTCondor version 8.7.6 released on January 4, 2018.

New Features:

    Changed the default value of configuration parameter IS_OWNER to False. The previous default value is now set as part of the use POLICY : Desktop configuration template. (Ticket #6463)

IS_OWNER = (START =?= False)

 

https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=6463

 

“The Owner state (and IS_OWNER) is an artifact of Condor's cycle-scavenging roots."

 

We ARE cycle scavenging from staff desktops/laptops. I assume if we explicitly set:

IS_OWNER = (START =?= False)

in the config files then the previous behaviour will be restored?

 

Thanks

 

Cheers

 

Greg

 

P.S. some more checking default configs show some other (maybe important?) differences.

 

8.6.12                                                                                              8.8.12

ADD_WINDOWS_FIREWALL_EXCEPTION = true                  ADD_WINDOWS_FIREWALL_EXCEPTION = false

CondorIsAdmin = true                                                                CondorIsAdmin = false

CURB_MATCHMAKING = false                                                 CURB_MATCHMAKING = RecentDaemonCoreDutyCycle > 0.98

 

I don’t think the matchmaking one will cause probs, and there’s a bunch of others to

do with concurrent uploads/downloads and negotiator max times that shouldn’t be an issue.