Looking for guidance on best place to control Job Executor’s selection of Jobs.
Given a cluster, I want to enforce through configuration which nodes in the cluster can work on which jobs.
Deployments are done through API/Database.
Thoughts?
Thanks
Hi @StephenOTT,
this topic belongs to JobAcquistion: The Job Executor | docs.camunda.org
For a cluster, the most important parameter is jobExecutorDeploymentAware
, which limits the jobs to the deployments done in the specific engine: The Job Executor | docs.camunda.org
JobAcquisition can be done with job priorities, and this could be a way to sort the important from the less important jobs.
Hope this helps, Ingo
@Ingo_Richtsmeier a priority would just cause a sort. But you are saying you could ignore jobs using priorities? An ignored job would be one that is never executed