treivize opened a new issue, #2260: URL: https://github.com/apache/incubator-kie-kogito-apps/issues/2260
### Describe the bug When using distributed job service (with Mongo DB persistency) to manage async task execution, there is a 1s delay introduced before each async task. ### Expected behavior No latency should be visible when job service is triggering an instant callback like for expired jobs or async callback. ### Actual behavior Job service code when scheduling a job apply a minimal delay of 1s which is not efficient for instant callback like for async task execution. I am doing reference of the following piece of codes: https://github.com/apache/incubator-kie-kogito-apps/blob/main/jobs-service/jobs-service-common/src/main/java/org/kie/kogito/jobs/service/scheduler/BaseTimerJobScheduler.java#L264 https://github.com/apache/incubator-kie-kogito-apps/blob/main/jobs-service/jobs-service-common/src/main/java/org/kie/kogito/jobs/service/scheduler/impl/VertxTimerServiceScheduler.java#L44 ### How to Reproduce? _No response_ ### Output of `uname -a` or `ver` _No response_ ### Output of `java -version` _No response_ ### GraalVM version (if different from Java) _No response_ ### Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM) _No response_ ### Build tool (ie. output of `mvnw --version` or `gradlew --version`) _No response_ ### Additional information _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
