Camunda in kubernetes cluster where the load distribution is not predictable

Hi,

I have 3 pods of Camunda in the kubernetes cluster. I have a main workflow which has multi-instance loop to execute parallel sub workflows. When the main workflow is started it creates multiple executable sub workflows. In most cases, only one pod executes all the sub workflows and the load is not distributed across pods. Due to this behaviour, there are pool exhausted exception and optimistic locking exception. Even after increasing the corepoolsize, maxpoolsize, maxactive still the exception occurs.

Is there any configuration or workflow change required to distribute the load across pods?

-Vishnu

1 Like