[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] MATLAB licenses
- Date: Thu, 9 Feb 2006 02:52:18 +0200
- From: Maxim Kovgan <maxim.kvg@xxxxxxxxx>
- Subject: Re: [Condor-users] MATLAB licenses
I can think of 2 directions:
1. you can wrap your matlab script into another script, which will
e.g. check how many licenses are left and poll the license server
until some threshold is reached, prior to launching matlab executable.
2. you can try using limits of maximum running jobs via the pool global macro:
MAX_JOBS_RUNNING, but then you need to make sure ... the only matlab
user runs this job.
3. If it is possible, you should obtain enough licenses to have the
whole pool busy.
On 2/9/06, Ben Liblit <liblit@xxxxxxxxxxx> wrote:
> I recently submitted a batch of 260 jobs, each of which runs two MATLAB
> batch scripts ("matlab -nojvm -nodisplay -r ...") toward the end of its
> work. 53 of these jobs failed because they were unable to obtain a
> MATLAB license:
> License Manager Error -4.
> Maximum number of users for MATLAB reached.
> Try again later.
> To see a list of current users use the lmstat utility.
> The MATLAB scripts are short, each lasting no more than a few seconds.
> But my 260 jobs include many subgroups of about equal duration, which
> means I'll be creating large spikes in MATLAB license demand.
> What's the right approach here? Is there a different way one is
> supposed to run MATLAB under Condor? Is there a way to declare the need
> for a MATLAB license as part of a job's classad restrictions? Should
> every Condor node have a specially reserved MATLAB license for the
> exclusive use of the Condor job it is currently running, or multiple
> such licenses for nodes that run multiple concurrent jobs?
> Condor-users mailing list