Expose Quartz underlying configuration in Quarkus/quartz for perfomance tuning

[fikrutm]

Currently we are using Quarkus/quartz cluster mode with store-type: jdbc_tx, in a situations where the scheduler has very large numbers of triggers that need to be fired at or near the same time.

Per quartz official documentation http://www.quartz-scheduler.org/documentation/quartz-2.3.0/configuration/ConfigMain.html#configuration-reference the performance expected to improve by setting:

org.quartz.scheduler.batchTriggerAcquisitionFireAheadTimeWindow (the larger the number, the more efficient firing is (in situations where there are very many triggers needing to be fired all at once)

org.quartz.scheduler.batchTriggerAcquisitionMaxCount (the larger the number, the more likely batch acquisition of triggers to fire will be able to select and fire more than 1 trigger at a time)

org.quartz.jobStore.acquireTriggersWithinLock (to avoid data corruption).

But Quarkus/quartz does not expose these properties as configurable. Would it be possible to expose the underlying default quartz configuration so that we can leverage the quartz batch mode?

Quartz provides these configurations: http://www.quartz-scheduler.org/documentation/quartz-2.3.0/configuration/ConfigMain.html
And Quarkus/Quartz provides these: https://quarkus.io/guides/quartz#quartz-configuration-reference

@cescoffier

[quarkus-bot]

/cc @machi1990, @mkouba

[geoand]

Seems reasonable to me

[machi1990]

Makes sense to me as well.

@fikrutm will you be interested in implementing it? We are happy and will be here to guide you. Thanks

[fikrutm]

@machi1990 I am glad to take the implementation, and needs a guide how to get started?

[machi1990]

Thanks @fikrutm

The configuration could be declared in https://github.com/quarkusio/quarkus/blob/main/extensions/quartz/runtime/src/main/java/io/quarkus/quartz/runtime/QuartzRuntimeConfig.java

The way it was done for https://github.com/quarkusio/quarkus/blob/main/extensions/quartz/runtime/src/main/java/io/quarkus/quartz/runtime/QuartzRuntimeConfig.java#L22-L32 could be used as inspiration.
The key thing to ensure is that the default value respects the current default behavior so that we do not break existing functionality.

As for property naming:

1. batchTriggerAcquisitionFireAheadTimeWindow
2. batchTriggerAcquisitionMaxCount
3. acquireTriggersWithinLock

Are okay names to me.
Ensure that the declared configuration are properly commented as they are used as documentation.

If this is your first time contributing to the repo, I'd suggest you to have a quick look at https://github.com/quarkusio/quarkus/blob/main/CONTRIBUTING.md

[machi1990]

Fixed by #29395