We got into a production incident where we are seeing below query fire consistency and causing to our CPU, what process would fire these queries? we dint had issues over last 1 year of running camunda.
we are on camunda 7.10 and using postgres as backed database
SELECT DISTINCT RES.*
FROM act_ru_execution RES
INNER JOIN act_re_procdef P
ON RES.proc_def_id_ = P.id_
WHERE RES.parent_id_ IS NULL
AND P.key_ = $1
AND RES.suspension_state_ = $2
AND EXISTS (SELECT id_
WHERE name_ = $3
AND RES.id_ = execution_id_
AND (( type_ IS NOT NULL
AND type_ = $4
AND long_ IS NOT NULL
AND long_ = $5 )))
ORDER BY RES.id_ ASC
LIMIT $6 offset $7
After further investigation, we were able to solve the issue by:
creating an index to the act_ru_variable table.
We identified that we were starting the camunda process too many times without the need to, so after revisiting the business logic we managed to reduce in more the half the number of times we started a process.
Also have Camunda (7.14) deployed to AWS RDS (Postgres).
Good to know you were able to solve this. we did add few additional indexes on act_ru_variable, act_ru_procinst and act_ru_ext_task tables on some of performance issues. We do have our database on RDS Postgress as well.
How are you deploying your app stack to AWS? are you using EC2 or Kubernetes?