Affects Version/s: 13.4.4
Fix Version/s: None
Job stauses and logs are stored forever in the permanent data folder. Most job logs are small, but others can grow to considerable individual sizes, e.g.:
Also, some job types have a more transient nature than others and, despite that, can end up taking the most space:
After a while, particularly for small storage restrictions, this can become a real problem.
We need a way to clean up these useless leftovers, either after a certain period or after a certain size and we also need a way to perform the cleanup preferentially, as some job logs might be needed on the long run (like the distribution job status, signaling that DW has executed), while others need to be deleted (like rendering).
Also, others do not necessarily grow (like wikicreation but can still end up consuming a considerable size without ever being actually useful and never being reclaimed. When the storage limit is 1GB, a 50MB wikicreation logs means 5%, which is a lot to drag around, including after upgrades.
The current workaround is for admins to create either a cron task or scheduled job that should perform the cleanup periodically.
A better solution would be if the product provides a configurable cleanup job with good defaults to address the most common issues.
An even more advanced step would be to do XWIKI-19215 and give full control and overview to admins over the jobs history and its impact on used storage.