Most jobs do not belong to an exclusion set. These jobs are typically the feature support jobs, as previously described, and they can co-exist and contend with any of the other jobs.

Non-exclusion jobs include:

• AVScan
• ChangelistCreate
• CloudPoolsLin/Treewalk
• ComplianceStoreDelete
• Dedupe
• DedupeDryRun
• DomainMark/Tag
• FilePolicy
• FSAnalyze
• IndexUpdate
• LinCount
• PermissionRepair
• QuotaScan
• ShadowStoreDelete
• SmartPoolsTree
• SnapshotDelete
• SnapRevert
• TreeDelete
• Undedupe
• WormQueue

Exclusion sets do not change the scope of the individual jobs themselves, so any runtime improvements from parallelism are the result of job management and impact control. The Job Engine monitors node CPU load and drive I/O activity per worker thread every 20 seconds to ensure that maintenance jobs do not cause cluster performance problems.

If a job affects overall system performance, the Job Engine reduces the activity of maintenance jobs and yields resources to clients. Impact policies limit the system resources that a job can consume and when a job can run. You can associate jobs with impact policies, ensuring that certain vital jobs always have access to system resources.

Figure 6.   OneFS Job Engine exclusion sets

Note: Job Engine exclusion sets are predefined and cannot be modified or reconfigured.