Scheduler: run multiple scheduler implementations

[mkouba]

• related to To be able to schedule clusterized tasks and non-clusterized (in memory) timers #41954

[vsevel]

excellent @mkouba
if I use multiple schedulers, how is defined the priority? is this the ordinal of the enum?
this means that today's Scheduled methods would continue running on the simple scheduler, whereas quartz would be used if explicitly specified in the executeWith attribute. correct?

[mkouba]

if I use multiple schedulers, how is defined the priority? is this the ordinal of the enum?
this means that today's Scheduled methods would continue running on the simple scheduler, whereas quartz would be used if explicitly specified in the executeWith attribute. correct?

Not really. Currently, the quarkus-quartz provides an implementation with higher priority (see also SchedulerImplementationBuildItem). Which means that if you have something like @Scheduled(every = "1s") then Quartz will be used automatically. @Scheduled(every = "1s", executeWith = Implementation.SIMPLE) means "always use the simple in-memory scheduler". If you use @Scheduled(every = "1s", executeWith = Implementation.QUARTZ) and quarkus-quartz is not available then the build fails (this part is not implemented yet ;-).

[mkouba]

If you use @Scheduled(every = "1s", executeWith = Implementation.QUARTZ) and quarkus-quartz is not available then the build fails (this part is not implemented yet ;-).

It's implemented and tested now.

[melloware]

Nice!

[mkouba]

@manovotn Thanks for approval. Still need to add some docs ;-)

[mkouba]

Do not merge yet, I have to add one more test for CompositeJobDefinition...

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit d4bd15a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit d4bd15a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 integration-tests/opentelemetry

✖ io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.testOTelInjections - History

• Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.reset(OpenTelemetryInjectionsTest.java:26)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)

---

⚙️ JVM Tests - JDK 21

📦 integration-tests/opentelemetry

✖ io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.testOTelInjections - History

• Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.reset(OpenTelemetryInjectionsTest.java:26)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

[github-actions]

🙈 The PR is closed and the preview is expired.