Disallow Concurrent execution of jobs belonging to same group

[Shazia Tabassum]

Hi,

For non-concurrent execution of jobs, I have found the following link:

http://jayvilalta.com/blog/2014/06/04/understanding-the-disallowconcurrentexecution-job-attribute/#comment-778971

It says that putting an attribute of [DisallowConcurrentExecutionAttribute] on the class which is implementing IJob, will ensure the non-concurrent execution of a single JOB INSTANCE i.e. based on a job key (job_name and job_group).

My requirement is to disallow the concurrent execution of ALL JOBS BELONGING TO THE SAME GROUP. Can anyone please help how it can be implemented? Does Quartz provide this feature or it needs custom implementation?

Regards,

Shazia.

[Marko Lahma]

This is not out of the box (and might not be so trivial to implement).
Maybe it would be easier to find a workaround if we'd knew the
original reasoning behind having a whole group of jobs disallowed to
fire concurrently.

Usually the case is that job implements functionality that needs
exclusive access and hence this configuration is done on job level.

-Marko

> --
> You received this message because you are subscribed to the Google Groups
> "Quartz.NET" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to quartznet+...@googlegroups.com.
> To post to this group, send email to quar...@googlegroups.com.
> Visit this group at http://groups.google.com/group/quartznet.
> For more options, visit https://groups.google.com/d/optout.
>

[Alex M]

Have there been changes since?

I have a similar requirement, i.e. the jobs from the same group should not be running in parallel.

[Marko Lahma]

Story is still the same, job key (name, group) forms the the lock for
concurrent execution. So no support for locking the whole group.

-Marko

> Visit this group at https://groups.google.com/group/quartznet.