Re: [HTCondor-users] Limit total STARTER log size across many slots?

[John M Knoeller <johnkn@xxxxxxxxxxx>]

Hi Max,

There is no way to do this within HTCondor while keeping a separate starter log per slot.  You could configure a shared starter log across all of the slots by configuring

STARTER_LOG_NAME_APPEND = false

https://htcondor.readthedocs.io/en/latest/admin-manual/configuration-macros.html#STARTER_LOG_NAME_APPEND

-tj

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Fischer, Max (SCC) <max.fischer@xxxxxxx>
Sent: Tuesday, January 30, 2024 6:45 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Limit total STARTER log size across many slots?

 

Hi all,

I’ve just dialled down `MAX_STARTER_LOG` since on our larger worker nodes (192-256 cores) logs were taking up unexpectedly much space. The reason for this is clear to us: For each core we get a `StarterLog.slot1_\d+` plus `StarterLog.slot1_\d+.old` - i.e. a worst case of up to 500 times  `MAX_STARTER_LOG`!
However, just reducing `MAX_STARTER_LOG` isn’t quite ideal. Due to differently sized jobs, `StarterLog.slot1_1` sees much more action than, say, `StarterLog.slot1_192` and the two rotate at wildly different rates (currently days versus months).

Are there any HTCondor knobs for limiting the total STARTER logs size while achieving a more uniform log rotation?

Cheers,
Max


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