defining only a SLOT_TYPE_2 should work, I'll have a look at the code, probably a silly bug.
-tj
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Larry Martell <larry.martell@xxxxxxxxx>
Sent: Thursday, January 25, 2024 6:20 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Slot configuration not starting with 1
Itâs not that we want to, itâs most likely a mistake by the person who was setting up that system, but it took us hours to find and fix the issue, and the fix was a total shot in the dark. So we are curious as to why that didnât work. Is such
a configuration not supported or is there some setting we need to support it?
Hi,
not sure if I got you right here - you want to define a SLOT_TYPE_2 but omit the type 1 ?
Why would that be a desireable thing ?
best
christoph
--
Christoph Beyer
DESY Hamburg
IT-Department
Notkestr. 85
Building 02b, Room 009
22607 Hamburg
phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
----- UrsprÃngliche Mail -----
Von: "Larry Martell" <larry.martell@xxxxxxxxx>
An: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
Gesendet: Mittwoch, 24. Januar 2024 19:58:57
Betreff: Re: [HTCondor-users] Slot configuration not starting with 1
On Wed, Jan 24, 2024 at 1:43âPM Beyer, Christoph
<christoph.beyer@xxxxxxx> wrote:
>
> Hi,
>
> don't expect much insight here without showing the slot configuration ;)
Basically we had this:
SLOT_TYPE_2 = cpus=15,memory=90%,disk=90%,gpus=0
And it would not come up saying there were 0 CPUs, memory, disk, and GPUs.
We changed it to:
SLOT_TYPE_1 = cpus=15,memory=90%,disk=90%,gpus=0
and it came up fine.
>
> ----- UrsprÃngliche Mail -----
> Von: "Larry Martell" <larry.martell@xxxxxxxxx>
> An: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
> Gesendet: Mittwoch, 24. Januar 2024 19:28:44
> Betreff: [HTCondor-users] Slot configuration not starting with 1
>
> We recently set up a system that had a slot 2 configured but not a
> slot 1. It failed to start and the StartLog showed there were no
> system resources at all available. It was like it allocated 100% of
> every resource to slot 1. Is this a known and documented thing?
|