Re: [HTCondor-users] History file rotation - reading from backups

[Jonathan Martin <JMartin@xxxxxxxxxxxx>]

Thanks Jaime, I actually didnât know condor_history looked through rotated files as well, I had just made an assumption based on the info in the docs:

 

If no history files are specified with the -file option, the local history file as specified in HTCondorâs configuration file ($(SPOOL)/history by default) is read.

 

I will go ahead and confirm that it is actually reading through backups as well, but it sounds like this is a non-issue.

 

Thanks,

Jon

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Jaime Frey
Sent: Wednesday, November 17, 2021 12:21 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] History file rotation - reading from backups

 

Are you able to adjust the history rotation configuration on these schedds? You can set the rotation trigger based on size or time, and the number of rotated files. condor_history (whether remote or local) should look through all of the rotated files automatically. If your remote condor_history queries arenât reading all of the rotated files, that sounds like a bug we should investigate.

 

 - Jaime

On Nov 17, 2021, at 12:48 PM, Jonathan Martin <JMartin@xxxxxxxxxxxx> wrote:

 

Hi,

 

Iâm building a data archiving system to warehouse historical job data and machine metrics, through various commands like condor_history and condor_status.

 

One issue Iâm facing is job history file rotation on remote condor schedds â by default, history files are rotated into backup files once they hit 20 MB. The system Iâm building is polling all schedds in the pool with a condor_history command every few minutes, but some jobs will slip through the cracks (history file gets rotated since last poll). Additionally, Iâm unable to retrieve the names of the backup files since the HTCondor folder on each schedd is not exposed via a network share.

 

Curious if there are any built-in config options that can help address this, without turning off rotation. Examples:

 

-          Overlap the last N jobs in the backup file and the new history file

-          Have condor_history additionally read through successive backup files until HISTORY_HELPER_MAX_HISTORY is hit (or reach end of all files)

 

Thanks,

Jon M

This communication (both the message and any attachments or links) is confidential and only intended for the use of the person or persons to whom it is addressed unless we have expressly authorized otherwise. It also may contain information that is protected by solicitor-client privilege. If you are reading this communication and are not an addressee or authorized representative of an addressee, we hereby notify you that any distribution, copying or other use of it without our express authorization is strictly prohibited. If you have received this communication in error, please delete both the message and any attachments from your system and notify us immediately by e-mail or phone. In addition, we note that this communication and its transmission of data have not been secured by encryption. Therefore, we are not able to confirm or guarantee that the communication has not been intercepted, amended, or read by an unintended third party.

_______________________________________________
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/

 

This communication (both the message and any attachments or links) is confidential and only intended for the use of the person or persons to whom it is addressed unless we have expressly authorized otherwise. It also may contain information that is protected by solicitor-client privilege. If you are reading this communication and are not an addressee or authorized representative of an addressee, we hereby notify you that any distribution, copying or other use of it without our express authorization is strictly prohibited. If you have received this communication in error, please delete both the message and any attachments from your system and notify us immediately by e-mail or phone. In addition, we note that this communication and its transmission of data have not been secured by encryption. Therefore, we are not able to confirm or guarantee that the communication has not been intercepted, amended, or read by an unintended third party.