Long Polling strategy for external tasks

Camunda 7 Topics Discussion & Questions
1

Hi there!

I’m using few java spring boot microservices and each of them is external client for camunda engine (for launching my service task implementations).
Camunda Engine is embedded option of one of my microservice, which store bpmn and have some rest api’s to start business processes.

However, time to time my microservice with camunda is down and at this time, all of my other microservices’re experiencing exceptionally high highloading, because of long polling. They’re trying to execute fetchAndLock, then they cannot do it, writting lot of logs with errors and my cluster (I’m using k8s in cloud) is very suffering.

Maybe I can switch some option and set timeout for between fetchAndLock requests or some another thing?

Thanks in advance!

2

Hi @MrFreezbe,

Are you using the Spring Boot Client for your external task workers? If so, you can implement a backoff-strategy:

Make sure that it is not disabled via the configuration.
Alternatively, think about using redundancy in your engine-setup. If you replicate your engine (both accessing the same database) one can crash and the traffic can be redirected to the other. See