[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] 7.8.3: "rejected by your job requirements" again

On 09/27/2012 09:58 AM, John (TJ) Knoeller wrote:
> If request_memory = 0,  or if it is any constant.   then your job will
> match based on the requested memory rather than on your actual memory usage.
> If you ask for 1k and use 2Gb, then your job can match 1k slots. Whether
> the slot will actually run your job or kick it off if it exceeds 1k memory
> usage depends on the slot's START and PREEMPT expressions.   The current 
> defaults for START and PREEMPT will let your job run to completion even
> if you use more memory than requested.
> If you don't specify request_memory in your submit file, then a default
> value is supplied
> request_memory = ifthenelse(MemoryUsage =!= undefined,MemoryUsage,(
> ImageSize + 1023 ) / 1024)
> This is a bit complicated, but in effect this is a request for memory
> that is based on the size of your executable before your job runs the 
> first time, and how much memory your job used in the previous run after
> it has run at least once.
> So the answer to your question is "It depends".   Whether or not you can
> set request_memory = 0 and have your jobs run depends in part on how the 
> pool is configured.   Condor is capable if being configured that way, and
> right now it is configured that way by default.

So effectively Condor does not support the Simple Stupid "just run this"
requirement: there is a way to request it, it may or may not stop (or
start) working after any condor_reconfig and/or condor update.

Is that the way it's designed to be or is it an unforseen side-effect of
adding more advanced sophisticated knobs?

Dimitri Maziuk
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Attachment: signature.asc
Description: OpenPGP digital signature