Jobs not executing concurrently, with a quartz error

[fishfacemcgee]

Bug description 🐞

When multiple jobs are created simultaneously, only one is executed at a time instead of concurrently. The logs on the API container included this:

2025-01-10T19:48:35.444Z ERROR 1 --- [SchedulerThread] org.quartz.core.ErrorLogger              : An error occurred while scanning for the next triggers to fire.

org.quartz.JobPersistenceException: Couldn't acquire next trigger: Cannot invoke "org.quartz.JobDetail.isConcurrentExecutionDisallowed()" because "job" is null
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2818) ~[quartz-2.5.0.jar:2.5.0]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.lambda$acquireNextTriggers$13(JobStoreSupport.java:2703) ~[quartz-2.5.0.jar:2.5.0]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3736) ~[quartz-2.5.0.jar:2.5.0]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTriggers(JobStoreSupport.java:2702) ~[quartz-2.5.0.jar:2.5.0]
	at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:294) ~[quartz-2.5.0.jar:2.5.0]
Caused by: java.lang.NullPointerException: Cannot invoke "org.quartz.JobDetail.isConcurrentExecutionDisallowed()" because "job" is null
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2769) ~[quartz-2.5.0.jar:2.5.0]
	... 4 common frames omitted

Steps to reproduce

Trigger multiple Terrakube workspace jobs in the same Organization. Most of our Terraform repos are mono repos (where each environment has its own workspace) so pushing a commit with common files modified is the easiest.

Expected behavior

Two or more workspaces run concurrently instead of one at a time.

Example repository

No response

Anything else?

No response

[alfespa17]

I think you are correct I was running 3 at the same time and the jobs were executed sequentially

I think it is related to this configuration

https://github.com/quartz-scheduler/quartz/blob/1d1f4c5bc2ebec1fa7bb0a8561088a8723c248aa/docs/configuration.adoc#configuration-of-jdbc-jobstoretx-store-jobs-and-triggers-in-a-database-via-jdbc

Specially using the following properties

org.quartz.scheduler.batchTriggerAcquisitionMaxCount
org.quartz.jobStore.acquireTriggersWithinLock

This could be updated in this file

terrakube/api/src/main/java/org/terrakube/api/plugin/scheduler/configuration/QuartzAutoConfiguration.java

Line 47 in 698439e

properties.put("org.quartz.jobStore.class","org.springframework.scheduling.quartz.LocalDataSourceJobStore");