Hi,
i have the problem, that our camunda database growes bigger and bigger and cleanup doesn´t delete anything. We use Camunda 7.8.0 with Tomcat. After looking in the history tables, i found out, that many entries belong to deployments/process definitions, which don’t exists anymore. Is there a way, that camunda cleans the tables, maybe with ttl?
@nashorn maybe https://docs.camunda.org/manual/7.8/user-guide/process-engine/history/#history-cleanup will help
kind regards,
ilias
Hi,
by “cleanup doesn’t delete anything” i meant history cleanup. I can not set TimeToLive for processdefinitions that do not exists anymore. Does Camunda clean up the history when a .war-file is deleted?
@nashorn You can configure either the History cleanup to run as a periodic task (https://docs.camunda.org/manual/7.8/user-guide/process-engine/history/#periodic-run) or run manually: (https://docs.camunda.org/manual/7.8/user-guide/process-engine/history/#manual-run)
Does this answer you question?
kind regards,
ilias
Hi,
thanks for your answer, but it doesn’t solve my problem. I already configured history cleanup as periodic task and started it manually, but as i said, cleanup didn’t delete the orphans. For examle the table ACT_HI_DETAIL is full of old VariableUpdate logs, where the PROC_DEF_ID_ references to processdefinitions which don’t exists anymore.