Background tasks
This page describes the management of background tasks running on Weka clusters.
The Weka system has some internal/external asynchronous operations and maintenance tasks, such as migrating an object store and downloading/uploading snapshots. These tasks are performed in the background and should not interfere with nor starve the Weka system from serving IOs with high performance.
The Weka system limits the CPU resources these tasks consume to 5% of the overall CPU.
Note: When the CPU is idle, background tasks can use more than the configured resources, but they are immediately freed if needed for serving IOs.
Note: The configured limit affects both external tasks (that are visible using the GUI/CLI) and internal low-priority asynchronous operations.
It is possible to view currently-running background tasks, including their status and progress.
Command:
weka cluster taskThis command is used for viewing all background tasks. For each task, a range of data can be displayed, as shown in the following example:
# weka cluster task
Type | State | Progress | Description
-----------+---------+----------+-----------------------------------------------------------
OBS_DETACH | RUNNING | 94 | Detaching Object Storage `obs_1` from filesystem `default`
It is possible to limit the resources being used by background tasks.
Command:
weka cluster task limitsThis command is used to view the defined limits.
Command:
weka cluster task limits set [--cpu-limit cpu-limit]This command is used to update the CPU limit.
It is possible to pause and later resume a background task, as well as completely abort it. This is useful in case there are other tasks/activities that are of higher priority.
Command:
weka cluster task pause / resume / abort <task-id>This command is used to pause/resume/abort the running of a specific task.
Note: Up to 16 background tasks can run in parallel. A paused (or aborting) task still consumes one of these spots.
Last modified 4mo ago