Open dsschult opened 8 years ago
How about we make a special classad in condor? If it is set, we take that number and transmit it with the job, otherwise we just set it to 14 hours?
Hello,
Coming back to this issue. MSU has this nice feature that it can potentially access a large number of resources in "backfill" mode as long as the requested walltime is less than 4h.
David, is Iceprod2 able to make use of the information that the glidein might have on remaining walltime in the slot and run payloads that match that time accordingly?
IceProd2 uses the TimeToLive
in the Rank expression, and sort-of uses that when matching. It's not strictly enforced yet because we don't have good estimates for the required time in place, so it's using a default value.
But sure, if MSU makes glideins that only live for 4 hours, that will probably work in most cases.
Let us try to ask OSG what ClassAd they are using for this (Vlad: EstimatedRunHours, may be?) and consider us using the same.
Think about a way to request a certain amount of walltime. Mostly, this should be used at the condor level to match to a glidein that will live for that length of time. Could also be used as a hint to short-time clusters like MSU.