Home > Storage > PowerScale (Isilon) > Product Documentation > Management and Migration > Storage Tiering with Dell PowerScale SmartPools > Job Engine
The Job Engine is OneFS’ parallel task scheduling framework, and is responsible for the distribution, execution, and impact management of critical jobs and operations across the entire cluster.
The OneFS Job Engine schedules and manages all the data protection and background cluster tasks: creating jobs for each task, prioritizing them and ensuring that internode communication and cluster-wide capacity utilization and performance are balanced and optimized. The Job Engine ensures that core cluster functions have priority over less important work. It gives applications integrated with OneFS the ability to control the priority of their various functions to ensure the best resource utilization. These applications can include add-on software or applications integrating with OneFS through the OneFS API.
Each job (such as the SmartPools job, for example) has an impact profile. An impact profile includes a configurable policy, a schedule that characterizes the amount of system resources the job will take, and an impact policy and impact schedule. The amount of work a job must perform is fixed. However, the resources dedicated to that work can be tuned to minimize the impact to other cluster functions, such as serving client data.
The SmartPools feature consists of the following jobs:
Job | Description |
SmartPools | Job that runs and moves data between the tiers of nodes within the same cluster. Also manages the CloudPools functionality if CloudPools is licensed and configured. |
SmartPoolsTree | Enforces SmartPools file policies on a subtree. |
FilePolicy | Efficient changelist-based SmartPools file pool policy job. |
IndexUpdate | Creates and updates an efficient file system index for the FilePolicy job. |
SetProtectPlus | Applies the default file policy. This job is disabled if SmartPools is activated on the cluster. |
Note: When a cluster running the FSAnalyze job is upgraded to OneFS 8.2 or later, the upgrade removes the legacy FSAnalyze index and snapshots. It replaces them with new snapshots the first time that IndexUpdate is run. The new index stores considerably more file and snapshot attributes than the old FSA index. Until the IndexUpdate job effects this change, FSA keeps running on the old index and snapshots.