search

camunda / camunda-bpm-platform

Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
https://camunda.com/
Apache License 2.0
4.11k stars 1.55k forks source link

historyTimeToLive can not set to null #3601

Closed spinachomes closed 1 year ago

spinachomes commented 1 year ago

Environment (Required on creation)

camunda:7.20.0-alpha3

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

in 7.20.0-alpha3 the process historyTimeToLive is required,I want to keep all history all the time ,so I set historyTimeToLive to null,but I get an error when deploy bpmn: Cannot parse historyTimeToLive: For input string: null | resource meeting_room.bpmn | line 4 | column 145

image

Steps to reproduce (Required on creation)

Observed Behavior (Required on creation)

Expected behavior (Required on creation)

Root Cause (Required on prioritization)

Solution Ideas

Hints

Links

Breakdown

### Pull Requests

Dev2QA handover

tasso94 commented 1 year ago

Hi @spinachomes,

You'll need a history time-to-live. Without history cleanup enabled, the history data of your executed processes will clutter the database and eventually negatively impact the engine's performance. Since the engine uses a relational database, only starting to clean up the history when a vast amount of data has been pilled up is very costly and time-consuming – in some situations, there is even no other solution than truncating tables and losing data.

You better proactively decide now for a reasonable time to live rather than fire-fighting later.

When really no history TTL is desired, the error can just be ignored. Nothing bad will happen other than an eventually bloated database. But this is highly discouraged.

Best, Tassilo

spinachomes commented 1 year ago

@tasso94 Thanks for your answer, I'll think about it again