We have an issue where history tables are growing in size and hence history/task API returning with a high response time. We need to partition the history tables keeping the data intact. Please suggest ways to achieve this.
1 Like
Hello @bhaswati_saikia,
Welcome to our forum!
Have you considered configuring the History cleanup on your system?
Blog post: T-Mobile Austria: lessons in successful database partitioning | Camunda
Best regards,
Yana
History cleanup is not desired now as we need to retain the history data for Business purpose
Hi @bhaswati_saikia,
By default, no cleanup window is configured. In that case, history cleanup is not performed automatically.
History and Audit Event Log | docs.camunda.org
I believe that what @Yana is trying to say is that having removal time column populated you can do table partitioning by it.
1 Like