When you install your cloud, the CleanCloud task is scheduled to run nightly.
CleanCloud identifies and deletes expired data from the cloud. Stored data about past actions or events is retained for a
preconfigured period (adjustable via the AlterCloud task), after which it is considered expired and is deleted.
Events are retained as follows:
Active events are not removed by CleanCloud.
Inactive events that have not been dismissed are removed after the retention period specified in the cloud properties.
Inactive events that have been dismissed are removed the next time CleanCloud is run.
batch_size This parameter controls how often the CleanCloud task performs a COMMIT. Larger transaction sizes are more efficient, but
in extreme cases could impact performance because of lock contention.
runtime_limit_length and runtime_limit_unit These parameters control how long the task is permitted to run. If the task deletes all expired data before the runtime limit
is exceeded, the runtime_limit_exceeded parameter equals 0. If the runtime limit is exceeded, the task immediately commits
and exits and the runtime_limit_exceeded parameter equals 1.
Runtime limits should only be specified in scenarios where a large volume of expired data may cause an unacceptably long running
time. For example, when CleanCloud has not been run for a long time, or immediately after altering the retention period. To
prevent continuous growth of the cloud, the CleanCloud task should be scheduled to run regularly with a runtime limit large
enough to allow the task to complete.