Multiple job groups in Quarkus Quartz

[AbhishekImp]

Description

When there are jobs with multiple groups. How can we run one group jobs on one instance and other group jobs on other instance.

Implementation ideas

No response

[quarkus-bot]

/cc @machi1990 (quartz), @manovotn (quartz), @mkouba (quartz)

[mkouba]

Hi @AbhishekImp and thanks for the report. I wonder if this is even possible with "vanilla" Quartz? I do not think so.

The only workaround I can think of is something along these lines:

1. Do not use the clustered mode,
2. Use a config property to define "active" groups/jobs, and
3. Use @Scheduled#skipExecutionIf() to skip execution for a job that does not match this config property.

(this should work with quarkus-scheduler too)

[AbhishekImp]

@mkouba : Can we alter or customize the query that we fire to get eligible jobs to be executed

[manovotn]

@mkouba : Can we alter or customize the query that we fire to get eligible jobs to be executed

Not sure I understand, Martin's suggestion should allow you to do just that?

Here's an example test using conditional execution. Yours would be similar except the condition would be based on a config property value which can differ in your deployment.

Or do you fire your jobs in some specific way that doesn't fit this?

[manovotn]

Hi @AbhishekImp and thanks for the report. I wonder if this is even possible with "vanilla" Quartz? I do not think so.

FTR, I also went looking for this in Quartz docs and didn't find anything like it.

[mkouba]

@mkouba : Can we alter or customize the query that we fire to get eligible jobs to be executed

Not sure I understand, Martin's suggestion should allow you to do just that?

I assume that @AbhishekImp is using persistent jobs (DB) and wants to modify the SQL query used to obtain the active triggers? I don't think that's possible.

The solution I proposed is a bit different in the sense that a job is triggered but the logic (e.g. @Scheduled method) is not executed.

[melloware]

Another option is just separate your Quarkus into two Quarkus apps one that has one set of Quartz jobs and one with the other and it allows you to share the Quartz tables and they are identified by their Instance ID. Not great but its better than anything hacky if you truly want to run jobs on specific instances...

[AbhishekImp]

How will we configure to pick separate jobs on separate instance using same quartz tables

…

On Thu, 28 Nov, 2024, 18:36 Melloware, ***@***.***> wrote: Another option is just separate your Quarkus into two Quarkus apps one that has one set of Quartz jobs and one with the other and it allows you to share the Quartz tables and they are identified by their Instance ID. Not great but its better than anything hacky if you truly want to run jobs on specific instances... — Reply to this email directly, view it on GitHub <#44800 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHDYYYYJPOMCL5RWBS6WKL2C4IOHAVCNFSM6AAAAABSU36PIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBWGA4DENJWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[melloware]

@AbhishekImp maybe you can start by clarifying WHAT you are trying to accomplish?

[AbhishekImp]

@mkouba @melloware : I have different kinds of jobs of multiple tenants(company). I want to specific different threads for different tenants so that one tenant cannot create a bottleneck for other tenant jobs

[melloware]

Ouch I do not think with Quartz you can do what you want to do. If they are separate tenants they should be seperate Quarkus apps with their own Quartz jobs