Table of Contents
- Introduction
- Setting up task prune via scheduler
Introduction
When you are integrating your systems, you may find a case where, for some reason, you have to put a big entity data into each task, for example, 25 KB per task. If that single route has generated 1 million tasks (before the task retention policy is triggered), your environment will consume 25 GB of database storage. Therefore, if your database storage capacity is 25 GB according to your Alumio license, the environment will have no more space to write any data. This will make the environment unavailable.
To prevent such an issue, Alumio provides functionality to prune tasks based on the criteria you can specify. This functionality is available as a job type of a scheduler.
Setting up task prune via scheduler
To set up pruning tasks, create a new Scheduler and navigate to the “Settings” option on the Scheduler details page.
In the “Job” dropdown, you can select the option “Prune tasks”.
Below, you can select the following options as well:
- Maximum age of tasks;
- Maximum number of tasks to keep;
- Routes
- Statuses
The “Maximum age of tasks” option allows you to specify the time the tasks have existed in the environment. For example, if you select seven days, tasks created more than seven days ago will be pruned.
The “Maximum number of tasks to keep” option allows you to specify the number of tasks you want to keep in the environment after the pruning. For example, if you set it to 100 and you have 1,000 tasks, the scheduler will prune 900 tasks and keep 100 in the environment.
The “Routes” option allows you to specify the route(s) whose tasks will be pruned. If you don’t select any route, it will prune tasks from any route.
The “Statuses” option allows you to specify the status(es) of the tasks that will be pruned. You can leave it empty to prune tasks with any status.
