Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Gyrex/Administrator Guide/Background Tasks"

(created to document disable of cleanup)
 
m (Maintenance)
Line 3: Line 3:
  
 
=== Maintenance ===
 
=== Maintenance ===
Out of the box, the job history is persisted in ZooKeeper. But that is not necessarily the right place for long term storage of a growing data set. Therefore, an automatic cleanup job will run once in awhile to remove old data from ZooKeeper.
+
Out of the box, the job history is persisted in ZooKeeper. But ZooKeeper is not the right place for long term storage of a growing data set. Therefore, an automatic cleanup job will run once in awhile to remove old data from ZooKeeper.
  
 
Automatic triggering of the cleanup job can be disabled by setting the system property <code>gyrex.jobs.cleanup.autotrigger.disabled=true</code>.
 
Automatic triggering of the cleanup job can be disabled by setting the system property <code>gyrex.jobs.cleanup.autotrigger.disabled=true</code>.

Revision as of 11:14, 15 April 2013

Background Task

TODO

Maintenance

Out of the box, the job history is persisted in ZooKeeper. But ZooKeeper is not the right place for long term storage of a growing data set. Therefore, an automatic cleanup job will run once in awhile to remove old data from ZooKeeper.

Automatic triggering of the cleanup job can be disabled by setting the system property gyrex.jobs.cleanup.autotrigger.disabled=true.

Back to the top