On Aug 25, 2015, at 1:26 PM, Jaime Frey <jfrey@xxxxxxxxxxx> wrote:On Aug 24, 2015, at 11:49 AM, Evan Sarmiento <esarmien@xxxxxxxxxxxxx> wrote:Hi All,I installed HTCondor 8.2.9 and turned on ALLOW_PSLOT_PREEMPTION by setting it to True on all my startds, schedds, and the negotiator. I have two startds configured as such:ALLOW_PSLOT_PREEMPTION = TrueNEGOTIATOR_USE_SLOT_WEIGHTS = trueNUM_SLOTS_TYPE_1 = 1SLOT_TYPE_1 = 100%SLOT_TYPE_1_PARTITIONABLE = TrueSLOT_WEIGHT = CpusSTARTD_SLOT_ATTRS =ÂHowever, when enabled, I canât get *any* pre-emption to occur. The Negotiator doesnât even attempt to pre-empt any jobs.When I turn off ALLOW_PSLOT_PREEMPTION, I can pre-empt like jobs that use the same resources as expected.Has anyone else run into this?I dug into the source code a little and it appears like jobs that want pslot preemption need âWantPslotPreemptionâ in the ClassAd request, just to make sure, I made a job like this and even set nice_user so it could defenitley be pre-empted by any other job, but, no pre-emption occurs.executable = /usr/bin/yesuniverse = vanillaoutput = /dev/nullerror = /dev/nulllog = /dev/nullnice_user = True+WantPslotPreemption = Truequeue 11Any ideas?First, the easy part: The WantPslotPreemption attribute is inserted by the schedd into the job ads that it sends to the negotiator to indicate that it understands a pslot preemption match, which involves claiming multiple slots on the execute machine. You shouldnât set it in your submit file.What form of preemption are you expecting thatâs not occurring with pslot preemption enabled, user priority-based or startd rank-based? I just did a quick test with startd rank-based preemption and it worked in my test pool.
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: