I recently migrated from 0.22 to 0.23. Earlier the job task completes within a second, but now after migration its taking more time the same code and the same BPMN workflow.
On the client side am using spring-zeebe and in fact i added the requesttimeout and pollinterval parameters but no luck, earlier in 0.22 i was not having these parameters though.
@jwulf : Yes I had logger on the worker and time taken is very minimal ~200ms.
What I noticed, although the step got activated on the engine around 10:13:13 and the job poller is running on interval of every 100ms, the job doesn’t reach the worker until 10:13:22:187 and once handed off worker completes the jobs within ms. Please see the screenshot attached.
As I have mentioned earlier the same workflow doesn’t have this problem with 0.22 version , I’m thinking if there is any configuration being missed on the engine or something else ?
@salaboy : Sure I have created an sample job, BPMN, HELM chart values used for engine .
Please let me know how do i attach the zip files , as alternate I have copied on the below location.
Please let me know if this is accessible.
What i observed is happening on the plain vanilla case is there some configuration introduced on the engine v0.23 which i missed or something else ?
Please see below the step activated on engine @ 12:04:48
Although the job worker had poll interval of one second [tried in ms as well] the job was picked by poller until 12:05:02 and worker is just simple log stmts.
@pumapathy can you add the code in a GitHub repository, it is way much better to review stuff than a zip file that I need to download. Please share that GitHub repo when you have it.