Scaling Heterogeneous Cluster With Deployment Aware Job Executor

Camunda 7 Topics Discussion & Questions
2

The configuration seems to work well; based on some initial tests with three server nodes and a single database

  1. Node 1 - TenantA
  2. Node 2 - TenantB
  3. Node 3 - TenantB

Each of the Nodes process engine configuration was modified to include the following configuration entry.

<!-- 
   	Fix for Keeping Jobs tied to the respective Process Engine & Tenant
	https://docs.camunda.org/manual/7.8/user-guide/process-engine/the-job-executor/#deployment-aware-job-executor
-->
<property name="jobExecutorDeploymentAware" value="true" />

I made sure that the latest deployment of the bpmn files was included in the War file as we use spring auto deployment.

I Started a new Process for Tenant B and then paused the Process at a specific part of my workflow using Remote Debugging in a Java Delegate. I then stopped the paused server -> the job executor on the second Tenant B instance then picked up the job up and completed it!

Perhaps someone has some experience with a similar setup?
Can anyone see any drawbacks to this setup?

1 Like