Re: [Condor-users] Setting concurrency limits for already running jobs

[Matthew Farrellee <matt@xxxxxxxxxx>]

On 06/20/2011 11:44 AM, Horvátth Szabolcs wrote:
> > You cannot change the concurrency limits of running jobs. You would
> > have to hold + change + release.
> That is a serious limitation of the system. Would be great if it was
> respected.
>
> > You can set limits at the same time you submit, so your second
> > sentence is a bit odd.
> My second sentence was about modifying the job class-ad after
> submission, using condor_qedit.
> Sometimes the limit has to be set after hours or days of job execution
> (for jobs that can't preempt/continue)
> so holding and releasing a job is not a viable option.
>
> Cheers,
> Szabolcs

http://spinningmatt.wordpress.com/2011/06/27/concurrency-limits-protecting-shared-resources/

It is a limitation, but typically it is difficult to determine when an 
executing program phase shifts and no longer requires a resource. You 
can make the shifts explicit with a DAG.

Possibly the recently mentioned condor_suspend/resume would be useful in 
your case.

FYI, it is architecturally possible to get jobs to release limits, via 
chirp or qedit, the ability just isn't implemented. A strong use case 
would be helpful.

Best,


matt