diff --git a/content/docs/1.6.0/deploy/important-notes/index.md b/content/docs/1.6.0/deploy/important-notes/index.md index f54cebf81..898126248 100644 --- a/content/docs/1.6.0/deploy/important-notes/index.md +++ b/content/docs/1.6.0/deploy/important-notes/index.md @@ -149,7 +149,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](../../references/settings/#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](../../references/settings/#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](../../references/settings/#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](../../references/settings/#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](../../references/settings/#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.0/references/helm-values.md b/content/docs/1.6.0/references/helm-values.md index 46f232868..e491acbe4 100644 --- a/content/docs/1.6.0/references/helm-values.md +++ b/content/docs/1.6.0/references/helm-values.md @@ -256,6 +256,6 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | diff --git a/content/docs/1.6.0/references/settings.md b/content/docs/1.6.0/references/settings.md index 9c7417698..75233c1ea 100644 --- a/content/docs/1.6.0/references/settings.md +++ b/content/docs/1.6.0/references/settings.md @@ -37,7 +37,7 @@ weight: 1 - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) - [V1 Data Engine](#v1-data-engine) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -443,12 +443,12 @@ The value in seconds specifies the timeout of the HTTP client to the replica's f Setting that allows you to enable the V1 Data Engine. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -754,7 +754,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.0/references/storage-class-parameters.md b/content/docs/1.6.0/references/storage-class-parameters.md index 018ea4428..112c68bc8 100644 --- a/content/docs/1.6.0/references/storage-class-parameters.md +++ b/content/docs/1.6.0/references/storage-class-parameters.md @@ -220,7 +220,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.6.0/v2-data-engine/_index.md b/content/docs/1.6.0/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.6.0/v2-data-engine/_index.md +++ b/content/docs/1.6.0/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.6.0/v2-data-engine/quick-start.md b/content/docs/1.6.0/v2-data-engine/quick-start.md index a160aa560..ae87dc47e 100644 --- a/content/docs/1.6.0/v2-data-engine/quick-start.md +++ b/content/docs/1.6.0/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.6.1/deploy/important-notes/index.md b/content/docs/1.6.1/deploy/important-notes/index.md index f38c0afe8..be9e57934 100644 --- a/content/docs/1.6.1/deploy/important-notes/index.md +++ b/content/docs/1.6.1/deploy/important-notes/index.md @@ -150,7 +150,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](../../references/settings/#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](../../references/settings/#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](../../references/settings/#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](../../references/settings/#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](../../references/settings/#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.1/references/helm-values.md b/content/docs/1.6.1/references/helm-values.md index 46f232868..e491acbe4 100644 --- a/content/docs/1.6.1/references/helm-values.md +++ b/content/docs/1.6.1/references/helm-values.md @@ -256,6 +256,6 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | diff --git a/content/docs/1.6.1/references/settings.md b/content/docs/1.6.1/references/settings.md index 9c7417698..75233c1ea 100644 --- a/content/docs/1.6.1/references/settings.md +++ b/content/docs/1.6.1/references/settings.md @@ -37,7 +37,7 @@ weight: 1 - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) - [V1 Data Engine](#v1-data-engine) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -443,12 +443,12 @@ The value in seconds specifies the timeout of the HTTP client to the replica's f Setting that allows you to enable the V1 Data Engine. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -754,7 +754,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.1/references/storage-class-parameters.md b/content/docs/1.6.1/references/storage-class-parameters.md index 018ea4428..112c68bc8 100644 --- a/content/docs/1.6.1/references/storage-class-parameters.md +++ b/content/docs/1.6.1/references/storage-class-parameters.md @@ -220,7 +220,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.6.1/v2-data-engine/_index.md b/content/docs/1.6.1/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.6.1/v2-data-engine/_index.md +++ b/content/docs/1.6.1/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.6.1/v2-data-engine/quick-start.md b/content/docs/1.6.1/v2-data-engine/quick-start.md index a160aa560..ae87dc47e 100644 --- a/content/docs/1.6.1/v2-data-engine/quick-start.md +++ b/content/docs/1.6.1/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.6.2/deploy/important-notes/index.md b/content/docs/1.6.2/deploy/important-notes/index.md index f38c0afe8..be9e57934 100644 --- a/content/docs/1.6.2/deploy/important-notes/index.md +++ b/content/docs/1.6.2/deploy/important-notes/index.md @@ -150,7 +150,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](../../references/settings/#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](../../references/settings/#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](../../references/settings/#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](../../references/settings/#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](../../references/settings/#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.2/references/helm-values.md b/content/docs/1.6.2/references/helm-values.md index 0f101f0e2..8f2d987b1 100644 --- a/content/docs/1.6.2/references/helm-values.md +++ b/content/docs/1.6.2/references/helm-values.md @@ -256,6 +256,6 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | diff --git a/content/docs/1.6.2/references/settings.md b/content/docs/1.6.2/references/settings.md index 9c7417698..75233c1ea 100644 --- a/content/docs/1.6.2/references/settings.md +++ b/content/docs/1.6.2/references/settings.md @@ -37,7 +37,7 @@ weight: 1 - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) - [V1 Data Engine](#v1-data-engine) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -443,12 +443,12 @@ The value in seconds specifies the timeout of the HTTP client to the replica's f Setting that allows you to enable the V1 Data Engine. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -754,7 +754,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.2/references/storage-class-parameters.md b/content/docs/1.6.2/references/storage-class-parameters.md index 018ea4428..112c68bc8 100644 --- a/content/docs/1.6.2/references/storage-class-parameters.md +++ b/content/docs/1.6.2/references/storage-class-parameters.md @@ -220,7 +220,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.6.2/v2-data-engine/_index.md b/content/docs/1.6.2/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.6.2/v2-data-engine/_index.md +++ b/content/docs/1.6.2/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.6.2/v2-data-engine/quick-start.md b/content/docs/1.6.2/v2-data-engine/quick-start.md index a160aa560..ae87dc47e 100644 --- a/content/docs/1.6.2/v2-data-engine/quick-start.md +++ b/content/docs/1.6.2/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.6.3/deploy/important-notes/index.md b/content/docs/1.6.3/deploy/important-notes/index.md index c0e04a517..9f35d7197 100644 --- a/content/docs/1.6.3/deploy/important-notes/index.md +++ b/content/docs/1.6.3/deploy/important-notes/index.md @@ -151,7 +151,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](../../references/settings/#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](../../references/settings/#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](../../references/settings/#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](../../references/settings/#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](../../references/settings/#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.3/references/helm-values.md b/content/docs/1.6.3/references/helm-values.md index 9622713b6..b7c9694a6 100644 --- a/content/docs/1.6.3/references/helm-values.md +++ b/content/docs/1.6.3/references/helm-values.md @@ -267,6 +267,6 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | diff --git a/content/docs/1.6.3/references/settings.md b/content/docs/1.6.3/references/settings.md index 47e844742..c049535cd 100644 --- a/content/docs/1.6.3/references/settings.md +++ b/content/docs/1.6.3/references/settings.md @@ -38,7 +38,7 @@ weight: 1 - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) - [V1 Data Engine](#v1-data-engine) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -453,12 +453,12 @@ The value in seconds specifies the timeout of the HTTP client to the replica's f Setting that allows you to enable the V1 Data Engine. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -764,7 +764,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.3/references/storage-class-parameters.md b/content/docs/1.6.3/references/storage-class-parameters.md index 018ea4428..112c68bc8 100644 --- a/content/docs/1.6.3/references/storage-class-parameters.md +++ b/content/docs/1.6.3/references/storage-class-parameters.md @@ -220,7 +220,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.6.3/v2-data-engine/_index.md b/content/docs/1.6.3/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.6.3/v2-data-engine/_index.md +++ b/content/docs/1.6.3/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.6.3/v2-data-engine/quick-start.md b/content/docs/1.6.3/v2-data-engine/quick-start.md index a160aa560..ae87dc47e 100644 --- a/content/docs/1.6.3/v2-data-engine/quick-start.md +++ b/content/docs/1.6.3/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.6.4/deploy/important-notes/index.md b/content/docs/1.6.4/deploy/important-notes/index.md index c93b8efec..6e26d3445 100644 --- a/content/docs/1.6.4/deploy/important-notes/index.md +++ b/content/docs/1.6.4/deploy/important-notes/index.md @@ -152,7 +152,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](../../references/settings/#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](../../references/settings/#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](../../references/settings/#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](../../references/settings/#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](../../references/settings/#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.4/references/helm-values.md b/content/docs/1.6.4/references/helm-values.md index 45a91ec31..8ae883ca3 100644 --- a/content/docs/1.6.4/references/helm-values.md +++ b/content/docs/1.6.4/references/helm-values.md @@ -271,6 +271,6 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | diff --git a/content/docs/1.6.4/references/settings.md b/content/docs/1.6.4/references/settings.md index 1250057e2..8ac6de06a 100644 --- a/content/docs/1.6.4/references/settings.md +++ b/content/docs/1.6.4/references/settings.md @@ -38,7 +38,7 @@ weight: 1 - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) - [V1 Data Engine](#v1-data-engine) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -453,12 +453,12 @@ The value in seconds specifies the timeout of the HTTP client to the replica's f Setting that allows you to enable the V1 Data Engine. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -764,7 +764,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.4/references/storage-class-parameters.md b/content/docs/1.6.4/references/storage-class-parameters.md index 018ea4428..112c68bc8 100644 --- a/content/docs/1.6.4/references/storage-class-parameters.md +++ b/content/docs/1.6.4/references/storage-class-parameters.md @@ -220,7 +220,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.6.4/v2-data-engine/_index.md b/content/docs/1.6.4/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.6.4/v2-data-engine/_index.md +++ b/content/docs/1.6.4/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.6.4/v2-data-engine/quick-start.md b/content/docs/1.6.4/v2-data-engine/quick-start.md index a160aa560..ae87dc47e 100644 --- a/content/docs/1.6.4/v2-data-engine/quick-start.md +++ b/content/docs/1.6.4/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.6.5/deploy/important-notes/index.md b/content/docs/1.6.5/deploy/important-notes/index.md index c93b8efec..6e26d3445 100644 --- a/content/docs/1.6.5/deploy/important-notes/index.md +++ b/content/docs/1.6.5/deploy/important-notes/index.md @@ -152,7 +152,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](../../references/settings/#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](../../references/settings/#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](../../references/settings/#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](../../references/settings/#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](../../references/settings/#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](../../references/settings/#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.5/references/helm-values.md b/content/docs/1.6.5/references/helm-values.md index 45a91ec31..8ae883ca3 100644 --- a/content/docs/1.6.5/references/helm-values.md +++ b/content/docs/1.6.5/references/helm-values.md @@ -271,6 +271,6 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | diff --git a/content/docs/1.6.5/references/settings.md b/content/docs/1.6.5/references/settings.md index 1250057e2..4b63e44d0 100644 --- a/content/docs/1.6.5/references/settings.md +++ b/content/docs/1.6.5/references/settings.md @@ -38,7 +38,7 @@ weight: 1 - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) - [V1 Data Engine](#v1-data-engine) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -453,12 +453,12 @@ The value in seconds specifies the timeout of the HTTP client to the replica's f Setting that allows you to enable the V1 Data Engine. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -764,7 +764,7 @@ Settings are synchronized hourly. When all volumes are detached, the settings in | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.6.5/references/storage-class-parameters.md b/content/docs/1.6.5/references/storage-class-parameters.md index 018ea4428..112c68bc8 100644 --- a/content/docs/1.6.5/references/storage-class-parameters.md +++ b/content/docs/1.6.5/references/storage-class-parameters.md @@ -220,7 +220,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.6.5/v2-data-engine/_index.md b/content/docs/1.6.5/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.6.5/v2-data-engine/_index.md +++ b/content/docs/1.6.5/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.6.5/v2-data-engine/quick-start.md b/content/docs/1.6.5/v2-data-engine/quick-start.md index a160aa560..ae87dc47e 100644 --- a/content/docs/1.6.5/v2-data-engine/quick-start.md +++ b/content/docs/1.6.5/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.7.0/references/helm-values.md b/content/docs/1.7.0/references/helm-values.md index 1a194dc6e..d6fee1cb4 100644 --- a/content/docs/1.7.0/references/helm-values.md +++ b/content/docs/1.7.0/references/helm-values.md @@ -271,7 +271,7 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | | defaultSettings.v2DataEngineLogFlags | Setting that allows you to configure the log flags of the SPDK target daemon (spdk_tgt) of the V2 Data Engine. | diff --git a/content/docs/1.7.0/references/settings.md b/content/docs/1.7.0/references/settings.md index bd77fdbce..c0616e1f8 100644 --- a/content/docs/1.7.0/references/settings.md +++ b/content/docs/1.7.0/references/settings.md @@ -41,7 +41,7 @@ weight: 1 - [Long gRPC Timeout](#long-grpc-timeout) - [V1 Data Engine](#v1-data-engine) - [RWX Volume Fast Failover (Experimental)](#rwx-volume-fast-failover-experimental) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -478,12 +478,12 @@ Setting that allows you to enable the V1 Data Engine. Enable improved ReadWriteMany volume HA by shortening the time it takes to recover from a node failure. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -834,7 +834,7 @@ If you do not detach all volumes before the settings are synchronized, the setti | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.7.0/references/storage-class-parameters.md b/content/docs/1.7.0/references/storage-class-parameters.md index 29efc7b2c..020c19a95 100644 --- a/content/docs/1.7.0/references/storage-class-parameters.md +++ b/content/docs/1.7.0/references/storage-class-parameters.md @@ -221,7 +221,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.7.0/v2-data-engine/_index.md b/content/docs/1.7.0/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.7.0/v2-data-engine/_index.md +++ b/content/docs/1.7.0/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.7.0/v2-data-engine/quick-start.md b/content/docs/1.7.0/v2-data-engine/quick-start.md index 79c53e5fb..799de67e6 100644 --- a/content/docs/1.7.0/v2-data-engine/quick-start.md +++ b/content/docs/1.7.0/v2-data-engine/quick-start.md @@ -29,7 +29,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.7.1/references/helm-values.md b/content/docs/1.7.1/references/helm-values.md index 1a194dc6e..d6fee1cb4 100644 --- a/content/docs/1.7.1/references/helm-values.md +++ b/content/docs/1.7.1/references/helm-values.md @@ -271,7 +271,7 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | | defaultSettings.v2DataEngineLogFlags | Setting that allows you to configure the log flags of the SPDK target daemon (spdk_tgt) of the V2 Data Engine. | diff --git a/content/docs/1.7.1/references/settings.md b/content/docs/1.7.1/references/settings.md index 55fd1f58d..cb7793508 100644 --- a/content/docs/1.7.1/references/settings.md +++ b/content/docs/1.7.1/references/settings.md @@ -41,7 +41,7 @@ weight: 1 - [Long gRPC Timeout](#long-grpc-timeout) - [V1 Data Engine](#v1-data-engine) - [RWX Volume Fast Failover (Experimental)](#rwx-volume-fast-failover-experimental) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -489,12 +489,12 @@ Setting that allows you to enable the V1 Data Engine. Enable improved ReadWriteMany volume HA by shortening the time it takes to recover from a node failure. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -845,7 +845,7 @@ If you do not detach all volumes before the settings are synchronized, the setti | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.7.1/references/storage-class-parameters.md b/content/docs/1.7.1/references/storage-class-parameters.md index 29efc7b2c..020c19a95 100644 --- a/content/docs/1.7.1/references/storage-class-parameters.md +++ b/content/docs/1.7.1/references/storage-class-parameters.md @@ -221,7 +221,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.7.1/v2-data-engine/_index.md b/content/docs/1.7.1/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.7.1/v2-data-engine/_index.md +++ b/content/docs/1.7.1/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.7.1/v2-data-engine/quick-start.md b/content/docs/1.7.1/v2-data-engine/quick-start.md index 79c53e5fb..799de67e6 100644 --- a/content/docs/1.7.1/v2-data-engine/quick-start.md +++ b/content/docs/1.7.1/v2-data-engine/quick-start.md @@ -29,7 +29,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.7.2/references/helm-values.md b/content/docs/1.7.2/references/helm-values.md index 181b89d27..49cbda441 100644 --- a/content/docs/1.7.2/references/helm-values.md +++ b/content/docs/1.7.2/references/helm-values.md @@ -271,7 +271,7 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | | defaultSettings.v2DataEngineLogFlags | Setting that allows you to configure the log flags of the SPDK target daemon (spdk_tgt) of the V2 Data Engine. | diff --git a/content/docs/1.7.2/references/settings.md b/content/docs/1.7.2/references/settings.md index fbc9544c4..cc4e56de2 100644 --- a/content/docs/1.7.2/references/settings.md +++ b/content/docs/1.7.2/references/settings.md @@ -41,7 +41,7 @@ weight: 1 - [Long gRPC Timeout](#long-grpc-timeout) - [V1 Data Engine](#v1-data-engine) - [RWX Volume Fast Failover (Experimental)](#rwx-volume-fast-failover-experimental) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -58,6 +58,7 @@ weight: 1 - [Backup Target](#backup-target) - [Backup Target Credential Secret](#backup-target-credential-secret) - [Backupstore Poll Interval](#backupstore-poll-interval) + - [Backup Execution Timeout](#backup-execution-timeout) - [Failed Backup Time To Live](#failed-backup-time-to-live) - [Cronjob Failed Jobs History Limit](#cronjob-failed-jobs-history-limit) - [Cronjob Successful Jobs History Limit](#cronjob-successful-jobs-history-limit) @@ -490,12 +491,12 @@ Setting that allows you to enable the V1 Data Engine. Enable improved ReadWriteMany volume HA by shortening the time it takes to recover from a node failure. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experiment feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -852,7 +853,7 @@ If you do not detach all volumes before the settings are synchronized, the setti | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.7.2/references/storage-class-parameters.md b/content/docs/1.7.2/references/storage-class-parameters.md index 29efc7b2c..020c19a95 100644 --- a/content/docs/1.7.2/references/storage-class-parameters.md +++ b/content/docs/1.7.2/references/storage-class-parameters.md @@ -221,7 +221,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.7.2/v2-data-engine/_index.md b/content/docs/1.7.2/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.7.2/v2-data-engine/_index.md +++ b/content/docs/1.7.2/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.7.2/v2-data-engine/quick-start.md b/content/docs/1.7.2/v2-data-engine/quick-start.md index 79c53e5fb..1e6238dc1 100644 --- a/content/docs/1.7.2/v2-data-engine/quick-start.md +++ b/content/docs/1.7.2/v2-data-engine/quick-start.md @@ -29,7 +29,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.7.3/references/helm-values.md b/content/docs/1.7.3/references/helm-values.md index 181b89d27..49cbda441 100644 --- a/content/docs/1.7.3/references/helm-values.md +++ b/content/docs/1.7.3/references/helm-values.md @@ -271,7 +271,7 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | | defaultSettings.v2DataEngineLogFlags | Setting that allows you to configure the log flags of the SPDK target daemon (spdk_tgt) of the V2 Data Engine. | diff --git a/content/docs/1.7.3/references/settings.md b/content/docs/1.7.3/references/settings.md index fbc9544c4..5d5a9347d 100644 --- a/content/docs/1.7.3/references/settings.md +++ b/content/docs/1.7.3/references/settings.md @@ -41,7 +41,7 @@ weight: 1 - [Long gRPC Timeout](#long-grpc-timeout) - [V1 Data Engine](#v1-data-engine) - [RWX Volume Fast Failover (Experimental)](#rwx-volume-fast-failover-experimental) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -58,6 +58,7 @@ weight: 1 - [Backup Target](#backup-target) - [Backup Target Credential Secret](#backup-target-credential-secret) - [Backupstore Poll Interval](#backupstore-poll-interval) + - [Backup Execution Timeout](#backup-execution-timeout) - [Failed Backup Time To Live](#failed-backup-time-to-live) - [Cronjob Failed Jobs History Limit](#cronjob-failed-jobs-history-limit) - [Cronjob Successful Jobs History Limit](#cronjob-successful-jobs-history-limit) @@ -490,12 +491,12 @@ Setting that allows you to enable the V1 Data Engine. Enable improved ReadWriteMany volume HA by shortening the time it takes to recover from a node failure. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -852,7 +853,7 @@ If you do not detach all volumes before the settings are synchronized, the setti | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.7.3/references/storage-class-parameters.md b/content/docs/1.7.3/references/storage-class-parameters.md index 29efc7b2c..020c19a95 100644 --- a/content/docs/1.7.3/references/storage-class-parameters.md +++ b/content/docs/1.7.3/references/storage-class-parameters.md @@ -221,7 +221,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.7.3/v2-data-engine/_index.md b/content/docs/1.7.3/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.7.3/v2-data-engine/_index.md +++ b/content/docs/1.7.3/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.7.3/v2-data-engine/quick-start.md b/content/docs/1.7.3/v2-data-engine/quick-start.md index 79c53e5fb..799de67e6 100644 --- a/content/docs/1.7.3/v2-data-engine/quick-start.md +++ b/content/docs/1.7.3/v2-data-engine/quick-start.md @@ -29,7 +29,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/1.8.0/important-notes/_index.md b/content/docs/1.8.0/important-notes/_index.md index 6acd4d744..d963de96c 100644 --- a/content/docs/1.8.0/important-notes/_index.md +++ b/content/docs/1.8.0/important-notes/_index.md @@ -116,7 +116,7 @@ For existing v2 volumes, users can update their setup by following these steps: - Back up the current v2 volumes. - Remove the v2 volumes. - Delete the block-type disk with a 4096-byte block size from `node.spec.disks`. -- Erase the old data on the block-type disk using tools such as wipefs or dd. +- Erase the old data on the block-type disk using tools such as `dd`. - Re-add the disk to `node.spec.disks` with the updated configuration. - Restore the v2 volumes. diff --git a/content/docs/1.8.0/references/helm-values.md b/content/docs/1.8.0/references/helm-values.md index 560143c4f..b0bbec6f5 100644 --- a/content/docs/1.8.0/references/helm-values.md +++ b/content/docs/1.8.0/references/helm-values.md @@ -272,7 +272,7 @@ During installation, you can either allow Longhorn to use the default system set | defaultSettings.taintToleration | Taint or toleration for system-managed Longhorn components. Specify values using a semicolon-separated list in `kubectl taint` syntax (Example: key1=value1:effect; key2=value2:effect). | | defaultSettings.upgradeChecker | Upgrade Checker that periodically checks for new Longhorn versions. When a new version is available, a notification appears on the Longhorn UI. This setting is enabled by default | | defaultSettings.v1DataEngine | Setting that allows you to enable the V1 Data Engine. | -| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. | +| defaultSettings.v2DataEngine | Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. | | defaultSettings.v2DataEngineGuaranteedInstanceManagerCPU | Number of millicpus on each node to be reserved for each Instance Manager pod when the V2 Data Engine is enabled. The default value is "1250". | | defaultSettings.v2DataEngineHugepageLimit | Setting that allows you to configure maximum huge page size (in MiB) for the V2 Data Engine. | | defaultSettings.v2DataEngineLogFlags | Setting that allows you to configure the log flags of the SPDK target daemon (spdk_tgt) of the V2 Data Engine. | diff --git a/content/docs/1.8.0/references/settings.md b/content/docs/1.8.0/references/settings.md index b1a267f72..d7faeb21d 100644 --- a/content/docs/1.8.0/references/settings.md +++ b/content/docs/1.8.0/references/settings.md @@ -41,7 +41,7 @@ weight: 1 - [Long gRPC Timeout](#long-grpc-timeout) - [V1 Data Engine](#v1-data-engine) - [RWX Volume Fast Failover (Experimental)](#rwx-volume-fast-failover-experimental) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [V2 Data Engine Hugepage Limit](#v2-data-engine-hugepage-limit) - [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) @@ -488,12 +488,12 @@ Setting that allows you to enable the V1 Data Engine. Enable improved ReadWriteMany volume HA by shortening the time it takes to recover from a node failure. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is a preview feature and should not be used in production environments. For more information, see [V2 Data Engine (Preview Feature)](../../v2-data-engine). +Setting that allows you to enable the V2 Data Engine, which is based on the Storage Performance Development Kit (SPDK). The V2 Data Engine is an experimental feature and should not be used in production environments. For more information, see [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > @@ -827,7 +827,7 @@ If you do not detach all volumes before the settings are synchronized, the setti | [System Managed Components Node Selector](#system-managed-components-node-selector) | [Node Selector](../../advanced-resources/deploy/node-selector/) | System-managed components | | [Storage Network](#storage-network) | [Storage Network](../../advanced-resources/deploy/storage-network/) | Instance Manager and Backing Image components | | [V1 Data Engine](#v1-data-engine) || Instance Manager component | - | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Preview Feature)](../../v2-data-engine/) | Instance Manager component | + | [V2 Data Engine](#v2-data-engine) | [V2 Data Engine (Experimental)](../../v2-data-engine/) | Instance Manager component | | [Guaranteed Instance Manager CPU](#guaranteed-instance-manager-cpu) || Instance Manager component | | [Guaranteed Instance Manager CPU for V2 Data Engine](#guaranteed-instance-manager-cpu-for-v2-data-engine) || Instance Manager component | diff --git a/content/docs/1.8.0/references/storage-class-parameters.md b/content/docs/1.8.0/references/storage-class-parameters.md index 29efc7b2c..020c19a95 100644 --- a/content/docs/1.8.0/references/storage-class-parameters.md +++ b/content/docs/1.8.0/references/storage-class-parameters.md @@ -221,7 +221,7 @@ A list of recurring jobs that are to be run on a volume. #### Data Engine *(field: `parameters.dataEngine`)* > Default: `"v1"` - - Specify "v2" to enable the V2 Data Engine (preview feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). + - Specify "v2" to enable the V2 Data Engine (experimental feature in v1.6.0). When unspecified, Longhorn uses the default value ("v1"). > Global setting: [V2 Data Engine](../settings#v2-data-engine). > More details in [V2 Data Engine Quick Start](../../v2-data-engine/quick-start#create-a-storageclass). diff --git a/content/docs/1.8.0/v2-data-engine/_index.md b/content/docs/1.8.0/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/1.8.0/v2-data-engine/_index.md +++ b/content/docs/1.8.0/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/1.8.0/v2-data-engine/quick-start.md b/content/docs/1.8.0/v2-data-engine/quick-start.md index 79c53e5fb..799de67e6 100644 --- a/content/docs/1.8.0/v2-data-engine/quick-start.md +++ b/content/docs/1.8.0/v2-data-engine/quick-start.md @@ -29,7 +29,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.0/references/settings.md b/content/docs/archives/1.5.0/references/settings.md index 483813192..8e9ee77ce 100644 --- a/content/docs/archives/1.5.0/references/settings.md +++ b/content/docs/archives/1.5.0/references/settings.md @@ -34,7 +34,7 @@ weight: 1 - [Support Bundle Failed History Limit](#support-bundle-failed-history-limit) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -396,12 +396,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.0/v2-data-engine/quick-start.md b/content/docs/archives/1.5.0/v2-data-engine/quick-start.md index 1de5d91ec..ca9cb62d4 100644 --- a/content/docs/archives/1.5.0/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.0/v2-data-engine/quick-start.md @@ -25,7 +25,7 @@ Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.1/references/settings.md b/content/docs/archives/1.5.1/references/settings.md index 483813192..8e9ee77ce 100644 --- a/content/docs/archives/1.5.1/references/settings.md +++ b/content/docs/archives/1.5.1/references/settings.md @@ -34,7 +34,7 @@ weight: 1 - [Support Bundle Failed History Limit](#support-bundle-failed-history-limit) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -396,12 +396,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.1/v2-data-engine/_index.md b/content/docs/archives/1.5.1/v2-data-engine/_index.md index 57bd357d4..3af20a1d5 100644 --- a/content/docs/archives/1.5.1/v2-data-engine/_index.md +++ b/content/docs/archives/1.5.1/v2-data-engine/_index.md @@ -1,4 +1,4 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 --- diff --git a/content/docs/archives/1.5.1/v2-data-engine/quick-start.md b/content/docs/archives/1.5.1/v2-data-engine/quick-start.md index 1de5d91ec..ca9cb62d4 100644 --- a/content/docs/archives/1.5.1/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.1/v2-data-engine/quick-start.md @@ -25,7 +25,7 @@ Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.2/references/settings.md b/content/docs/archives/1.5.2/references/settings.md index 5d768f1d6..5203483b3 100644 --- a/content/docs/archives/1.5.2/references/settings.md +++ b/content/docs/archives/1.5.2/references/settings.md @@ -34,7 +34,7 @@ weight: 1 - [Support Bundle Failed History Limit](#support-bundle-failed-history-limit) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -396,12 +396,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.2/v2-data-engine/_index.md b/content/docs/archives/1.5.2/v2-data-engine/_index.md index 57bd357d4..3af20a1d5 100644 --- a/content/docs/archives/1.5.2/v2-data-engine/_index.md +++ b/content/docs/archives/1.5.2/v2-data-engine/_index.md @@ -1,4 +1,4 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 --- diff --git a/content/docs/archives/1.5.2/v2-data-engine/quick-start.md b/content/docs/archives/1.5.2/v2-data-engine/quick-start.md index d62a5b410..c83afc873 100644 --- a/content/docs/archives/1.5.2/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.2/v2-data-engine/quick-start.md @@ -25,7 +25,7 @@ Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.3/references/settings.md b/content/docs/archives/1.5.3/references/settings.md index 5d768f1d6..5203483b3 100644 --- a/content/docs/archives/1.5.3/references/settings.md +++ b/content/docs/archives/1.5.3/references/settings.md @@ -34,7 +34,7 @@ weight: 1 - [Support Bundle Failed History Limit](#support-bundle-failed-history-limit) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -396,12 +396,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.3/v2-data-engine/_index.md b/content/docs/archives/1.5.3/v2-data-engine/_index.md index fea1007d8..eedb32b6e 100644 --- a/content/docs/archives/1.5.3/v2-data-engine/_index.md +++ b/content/docs/archives/1.5.3/v2-data-engine/_index.md @@ -1,5 +1,5 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 aliases: - /spdk/_index.md diff --git a/content/docs/archives/1.5.3/v2-data-engine/quick-start.md b/content/docs/archives/1.5.3/v2-data-engine/quick-start.md index 2983d48c8..dfae569cb 100644 --- a/content/docs/archives/1.5.3/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.3/v2-data-engine/quick-start.md @@ -27,7 +27,7 @@ aliases: Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.4/references/settings.md b/content/docs/archives/1.5.4/references/settings.md index 298d7635f..be740e005 100644 --- a/content/docs/archives/1.5.4/references/settings.md +++ b/content/docs/archives/1.5.4/references/settings.md @@ -34,7 +34,7 @@ weight: 1 - [Support Bundle Failed History Limit](#support-bundle-failed-history-limit) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -410,12 +410,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.4/v2-data-engine/_index.md b/content/docs/archives/1.5.4/v2-data-engine/_index.md index 57bd357d4..3af20a1d5 100644 --- a/content/docs/archives/1.5.4/v2-data-engine/_index.md +++ b/content/docs/archives/1.5.4/v2-data-engine/_index.md @@ -1,4 +1,4 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 --- diff --git a/content/docs/archives/1.5.4/v2-data-engine/quick-start.md b/content/docs/archives/1.5.4/v2-data-engine/quick-start.md index d62a5b410..c83afc873 100644 --- a/content/docs/archives/1.5.4/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.4/v2-data-engine/quick-start.md @@ -25,7 +25,7 @@ Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.5/references/settings.md b/content/docs/archives/1.5.5/references/settings.md index 298d7635f..be740e005 100644 --- a/content/docs/archives/1.5.5/references/settings.md +++ b/content/docs/archives/1.5.5/references/settings.md @@ -34,7 +34,7 @@ weight: 1 - [Support Bundle Failed History Limit](#support-bundle-failed-history-limit) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -410,12 +410,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.5/v2-data-engine/_index.md b/content/docs/archives/1.5.5/v2-data-engine/_index.md index 57bd357d4..3af20a1d5 100644 --- a/content/docs/archives/1.5.5/v2-data-engine/_index.md +++ b/content/docs/archives/1.5.5/v2-data-engine/_index.md @@ -1,4 +1,4 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 --- diff --git a/content/docs/archives/1.5.5/v2-data-engine/quick-start.md b/content/docs/archives/1.5.5/v2-data-engine/quick-start.md index d62a5b410..c83afc873 100644 --- a/content/docs/archives/1.5.5/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.5/v2-data-engine/quick-start.md @@ -25,7 +25,7 @@ Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume diff --git a/content/docs/archives/1.5.6/references/settings.md b/content/docs/archives/1.5.6/references/settings.md index 3e4dd0995..c0d527bee 100644 --- a/content/docs/archives/1.5.6/references/settings.md +++ b/content/docs/archives/1.5.6/references/settings.md @@ -35,7 +35,7 @@ weight: 1 - [Support Bundle Node Collection Timeout](#support-bundle-node-collection-timeout) - [Fast Replica Rebuild Enabled](#fast-replica-rebuild-enabled) - [Timeout of HTTP Client to Replica File Sync Server](#timeout-of-http-client-to-replica-file-sync-server) -- [V2 Data Engine (Preview Feature)](#v2-data-engine-preview-feature) +- [V2 Data Engine (Experimental)](#v2-data-engine-experimental) - [V2 Data Engine](#v2-data-engine) - [Offline Replica Rebuilding](#offline-replica-rebuilding) - [Snapshot](#snapshot) @@ -420,12 +420,12 @@ The setting enables fast replica rebuilding feature. It relies on the checksums The value in seconds specifies the timeout of the HTTP client to the replica's file sync server used for replica rebuilding, volume cloning, snapshot cloning, etc. -### V2 Data Engine (Preview Feature) +### V2 Data Engine (Experimental) #### V2 Data Engine > Default: `false` -This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Preview Feature)](../../v2-data-engine). +This allows users to activate the v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment. For more information, please refer to [V2 Data Engine (Experimental)](../../v2-data-engine). > **Warning** > diff --git a/content/docs/archives/1.5.6/v2-data-engine/_index.md b/content/docs/archives/1.5.6/v2-data-engine/_index.md index 57bd357d4..3af20a1d5 100644 --- a/content/docs/archives/1.5.6/v2-data-engine/_index.md +++ b/content/docs/archives/1.5.6/v2-data-engine/_index.md @@ -1,4 +1,4 @@ --- -title: V2 Data Engine (Preview Feature) +title: V2 Data Engine (Experimental) weight: 0 --- diff --git a/content/docs/archives/1.5.6/v2-data-engine/quick-start.md b/content/docs/archives/1.5.6/v2-data-engine/quick-start.md index d62a5b410..c83afc873 100644 --- a/content/docs/archives/1.5.6/v2-data-engine/quick-start.md +++ b/content/docs/archives/1.5.6/v2-data-engine/quick-start.md @@ -25,7 +25,7 @@ Longhorn's V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to elevate its overall performance. The integration significantly reduces I/O latency while simultaneously boosting IOPS and throughput. The enhancement provides a high-performance storage solution capable of meeting diverse workload demands. -**V2 Data Engine is currently a PREVIEW feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports +**V2 Data Engine is currently an Experimental feature and should NOT be utilized in a production environment.** At present, a volume with V2 Data Engine only supports - Volume lifecycle (creation, attachment, detachment and deletion) - Degraded volume