-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Context:
We recently saw some Jenkins jobs running into an out of memory due to a huge increase in job log size. This was caused by the recent changes with OPT-4612 that logged all ids to be updated/deleted which can be in the magnitude of 10k.
AT:
- only log the count of ids instead of every single id on deleteBy/updateBy queries
Hint:
For the excessive log, see e.g. https://ci.optimize.camunda.cloud/job/event-cleanup-performance/201/consoleText