Re: [HTCondor-users] Are evicted jobs memory requirements automatically adjusted?

["John (TJ) Knoeller" <johnkn@xxxxxxxxxxx>]

As HTCondor is configured by default it's 5a.   If you want 5b the job should have

    RequestMemory = Max(500, MemoryUsage)

But you probably don't really want that.   Jobs that have MemoryUsage > RequestMemory should
probably not match anything until the user intervenes and sets RequestMemory correctly. 

Keep in mind that jobs that lie about memory usage like this are  waste time on larger and
larger slots as they hunt for a slot that can accommodate them.  

-tj

On 2/6/2013 8:48 AM, Chris Filo Gorgolewski wrote:

When a job gets suspended and evicted it's memory requirements adjusted by the actual values measured during it's execution?

For example:

1. I job with "request_memory = 500" is being submitted.

2. The job gets assigned to a node, starts running.

3. It allocates 2000MB.

4. The job gets suspended and evicted (reason does not really matter in this example)

5a. Job gets resubmitted to another node with memory requirement of 500MB (as requested by the user)

5b. Job gets resubmitted to another node with memory requirement of 2000MB (as measured during previous execution)

So which one is it 5a or 5b?

If 5a how can I achieve 5b (increasing the memory requirements by the maximum memory allocation from the previous failed execution)?

This is especially important when using policy described here: https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=HowToLimitMemoryUsage

Thanks in advance!

Best,

Chris

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