We recently enacted a workflow to clean up old jobs to improve author instance
performance. We are using TarMK for persistence, but our repo is on the order
of 20GB in size.
We have noticed we need to run OAK offline compaction jobs with AEM6.1 because
the repository does appear to grow faster
To: users@sling.apache.org
Subject: RE: Old jobs in repository
there is a built-in job consumer to cleanup historic job data from the
repository, this should include cancelled jobs.
it's not active by default.
you can use the job api to run this job - example:
String JOB_HISTORY_CLEANUP_TOPIC
there is a built-in job consumer to cleanup historic job data from the
repository, this should include cancelled jobs.
it's not active by default.
you can use the job api to run this job - example:
String JOB_HISTORY_CLEANUP_TOPIC =
"org/apache/sling/event/impl/jobs/tasks/HistoryCleanUpTask";
