Re: [HTCondor-users] Recording slot attributes in condor_history

[John M Knoeller <johnkn@xxxxxxxxxxx>]

Please do not set attributes that start with the word SYSTEM_ in your configuration.

 

Use JOB_MACHINE_ATTRS, etc instead.

 

Attributes that start with SYSTEM_ exist so that the HTCondor team can change defaults without colliding with your configuration.

 

-tj

 

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Tom Downes
Sent: Saturday, April 15, 2017 7:49 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Recording slot attributes in condor_history

 

Vlad:

 

What you want are SYSTEM_JOB_MACHINE_ATTRS and SYSTEM_JOB_MACHINE_ATTRS_HISTORY_LENGTH. It's a scheduler configuration documented in section 3.5.10 of the 8.6.1 manual. Obviously choose the appropriate manual for your version, but I don't think it's changed much.

--

Tom Downes
Senior Scientist and Data Center Manager
Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin-Milwaukee
414.229.2678

 

On Sat, Apr 15, 2017 at 4:24 PM, Vladimir Brik <vladimir.brik@xxxxxxxxxxxxxxxx> wrote:

Hello,

Is is possible to have Condor record for each completed job in its history values of arbitrary slot attributes that that job ran on?

For example, if job completed running on a slot that advertises attribute SLOT_INFO, is it possible to get condor_history to display the value of that attribute?

Even better, if a job is restarted multiple times, is it possible to get a list of SLOT_INFO values of each slot it ran on?


Thanks,

Vlad
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/