OneFS does not automatically select LIN-based jobs if those jobs are more efficient to run

Summary: OneFS does not automatically select LIN-based jobs if these would be more efficient to run where SSD is set to metadata rather than L3 cache.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

SSDs on a cluster are configured to be used for Metadata rather than L3 cache.

In theory, this means that jobs such as FlexProtect and AutoBalance would run faster and more efficiently if their LIN-equivalents were selected (FlexProtectLIN and AutotBalanceLIN). This is because the metadata on the SSDs can be leveraged by the job engine. 

The regular versions of the job automatically trigger when required by OneFS instead of the LIN version.

The White Paper on the OneFS job engine states: 
"There is also an AutoBalanceLin job available, which is *automatically* run in place of AutoBalance when the cluster has a metadata copy available on SSD. AutoBalanceLin provides an expedited job runtime." 

https://www.delltechnologies.com/resources/en-us/asset/white-papers/products/storage/h12570-wp-isilon-onefs-job-engine.pdf

With PSCALE-104758, the automatically part is not true.
Instead it is a manual configuration using.
# isi_gconfig -t job-config jobs.common.lin_based_jobs=True

Cause

This is due to a OneFS code issue.

Resolution

Manually set the "run LIN-based jobs" to true in cluster settings.
# isi_gconfig -t job-config jobs.common.lin_based_jobs=True
Consider disabling non-LIN based jobs.

Affected Products

Isilon, Isilon, Isilon Gen6.5, Isilon Gen6, Isilon SmartPools
Article Properties
Article Number: 000212030
Article Type: Solution
Last Modified: 23 Apr 2024
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.