In the 25.x feature branch (going to the 26.0.x LTS), HTCondor has introduced three classads that we would like to give users access to:
- retry_request_memory
- retry_request_memory_increase
- retry_request_memory_max
We should provide access to these classads via flags for jobsub_submit. The idea would be to simply translate the values to classads.
See the condor docs for more details: https://htcondor.readthedocs.io/en/latest/man-pages/condor_submit.html#retry_request_memory
Currently, users give a set of flags to mimic this behavior:
- FERMIHTC_AutoRelease
- FERMIHTC_GraceMemory
To maintain backward compatibility, we should figure out exactly how these work (I believe they are handled by job transforms on the schedds), and map something like a user input of --lines FERMIHTC_GraceMemory=20GB to --retry_request_memory=(request_memory + 20GB), where we do the calculation for them.
In the 25.x feature branch (going to the 26.0.x LTS), HTCondor has introduced three classads that we would like to give users access to:
We should provide access to these classads via flags for
jobsub_submit. The idea would be to simply translate the values to classads.See the condor docs for more details: https://htcondor.readthedocs.io/en/latest/man-pages/condor_submit.html#retry_request_memory
Currently, users give a set of flags to mimic this behavior:
To maintain backward compatibility, we should figure out exactly how these work (I believe they are handled by job transforms on the schedds), and map something like a user input of
--lines FERMIHTC_GraceMemory=20GBto--retry_request_memory=(request_memory + 20GB), where we do the calculation for them.