Re: [HTCondor-users] Preventing users from submitting too many jobs

[Brian Bockelman <bbockelm@xxxxxxxxxxx>]

Hi Vlad,

How âbulletproofâ do you want this to be?

In your idea below, Iâd point out that âcondor_status -submitterâ is more lightweight than âcondor_qâ.  However, the information available via condor_status is only updated once every 5 minutes.

There have been proposed improvements to SUBMIT_REQUIREMENTS that would make the per-submitter information available to the expression.  Nothing has moved off the drawing board, however.

Brian

> On May 27, 2015, at 8:30 AM, Vladimir Brik <vladimir.brik@xxxxxxxxxxxxxxxx> wrote:
> 
> Hello,
> 
> I would like to have a mechanism to prevent a user from submitting new jobs if he or she already has a large number of jobs in the queue (e.g. >20,000).
> 
> SUBMIT_MAX_PROCS_IN_CLUSTER and MAX_JOBS_SUBMITTED help, but don't solve the problem completely because they are global limits, and I'd like to have per-user limits.
> 
> What I am thinking of doing is replacing condor_submit with a wrapper that runs condor_q to check if the user submitted too many jobs, and if so, drops a config file with appropriate SUBMIT_REQUIREMENT_* to block the user from submitting more. The wrapper would be clever enough to skip condor_q if its called too frequently.
> 
> Does anybody know of a simpler way to have per-user limits on the number of jobs in queue?
> 
> Is there a way to do something similar for jobs submitted using python bindings and/or remote submissions?
> 
> 
> Thanks,
> 
> Vlad
> _______________________________________________
> 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/