Re: [HTCondor-users] question on late materialization shadows

[John M Knoeller <johnkn@xxxxxxxxxxx>]

There is a old mechanism where a job can request in the submit file that a list of attributes be copied from the STARTD ad to the job ad at the time the AP decides to run that job on a specific machine.  This happens after the slot is claimed, just before the shadow is created.

The submit keyword is job_machine_attrs

There is a new mechanism in 10.6 where a job can request that a list of attributes from the STARTD ad be printed in the job's log file as a part of the execute event in that file.  The submit keyword for this is ulog_execute_event_attrs


-----Original Message-----
From: Thomas Hartmann <thomas.hartmann@xxxxxxx> 
Sent: Wednesday, August 9, 2023 9:02 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Cc: John M Knoeller <johnkn@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] question on late materialization shadows

Hi TJ,

ah, OK - I had interpreted too much into the shadow messages and the 
user's late materialization was just bad luck ð

Is there a way to add starter ads to a job's ads but only for actual 
matched shadows+starters?
AFAIS the job ads are updated each negotiation cycle with a proposed EPs 
ads - even if the EP is rejecting(?) the job and the job got backed off 
waiting for the next cycle.

Cheers and thanks,
   Thomas