ivampiresp/longhorn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Highlight CPU usage in v2-data-engine setting

Browse Source 
Longhorn 6126

Signed-off-by: Derek Su <derek.su@suse.com>
(cherry picked from commit 46e1bb2cc3)
This commit is contained in:
Derek Su 2023-06-20 13:37:19 +08:00 committed by David Ko
parent e462d7cdd1
commit e9310044ce
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chart/questions.yaml
View File

@ -689,9 +689,9 @@ Set the value to **0** to disable backup restore."
label: V2 Data Engine
description: "This allows users to activate v2 data engine based on SPDK. Currently, it is in the preview phase and should not be utilized in a production environment.
WARNING:
- The cluster must have pre-existing Multus installed, and NetworkAttachmentDefinition IPs are reachable between nodes.
- DO NOT CHANGE THIS SETTING WITH ATTACHED VOLUMES. Longhorn will block this setting update when there are attached volumes.
- When applying the setting, Longhorn will restart all instance-manager pods."
- When applying the setting, Longhorn will restart all instance-manager pods.
- When the V2 Data Engine is enabled, each instance-manager pod utilizes 1 CPU core. This high CPU usage is attributed to the spdk_tgt process running within each instance-manager pod. The spdk_tgt process is responsible for handling input/output (IO) operations and requires intensive polling. As a result, it consumes 100% of a dedicated CPU core to efficiently manage and process the IO requests, ensuring optimal performance and responsiveness for storage operations."
group: "Longhorn V2 Data Engine (Preview Feature) Settings"
type: boolean
default: false