Hi Cole,
I was reading email backwards (most recent first) so I only see this now, after writing about this feature not seeming to work with DagMan.
The use case is that a dag is controlling some submission of job clusters, each cluster containing several hundred subjobs. We want the max idle feature to limit the number of queued jobs in these subclusters. It does not, so we wind up having very very many jobs that the negotiator has to go through each cycle.
Is that enough information?
JT On 20 Dec 2024, at 18:26, Cole Bollig via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:
Hi All,
For those of you that interact in DAGMan in some fashion regularly, do you use the -maxidle command line option or the DAGMAN_MAX_JOBS_IDLE configuration option. If so, what was the use case that brought about you setting one of these options?
Cheers, DAGMan Developer at CHTC Cole Bollig _______________________________________________HTCondor-users mailing listTo unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with asubject: UnsubscribeThe archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/
|