chart: Add new setting 'Concurrent Replica Rebuild Per Node Limit'

Longhorn 2460

Signed-off-by: Shuo Wu <shuo.wu@suse.com>
This commit is contained in:
Shuo Wu 2021-09-16 19:39:22 +08:00 committed by David Ko
parent d4728f44df
commit ecc529569d
3 changed files with 9 additions and 0 deletions

View File

@ -391,6 +391,13 @@ Warning: This option works only when there is a failed replica in the volume. An
type: int type: int
min: 0 min: 0
default: 600 default: 600
- variable: defaultSettings.concurrentReplicaRebuildPerNodeLimit
label: Concurrent Replica Rebuild Per Node Limit
description: "This setting controls how many replicas on a node can be rebuilt simultaneously. If the value is 0, Longhorn will not limit the rebuilding."
group: "Longhorn Default Settings"
type: int
min: 0
default: 0
- variable: defaultSettings.disableRevisionCounter - variable: defaultSettings.disableRevisionCounter
label: Disable Revision Counter label: Disable Revision Counter
description: "This setting is only for volumes created by UI. By default, this is false meaning there will be a reivision counter file to track every write to the volume. During salvage recovering Longhorn will pick the repica with largest reivision counter as candidate to recover the whole volume. If revision counter is disabled, Longhorn will not track every write to the volume. During the salvage recovering, Longhorn will use the 'volume-head-xxx.img' file last modification time and file size to pick the replica candidate to recover the whole volume." description: "This setting is only for volumes created by UI. By default, this is false meaning there will be a reivision counter file to track every write to the volume. During salvage recovering Longhorn will pick the repica with largest reivision counter as candidate to recover the whole volume. If revision counter is disabled, Longhorn will not track every write to the volume. During the salvage recovering, Longhorn will use the 'volume-head-xxx.img' file last modification time and file size to pick the replica candidate to recover the whole volume."

View File

@ -32,6 +32,7 @@ data:
mkfs-ext4-parameters: {{ .Values.defaultSettings.mkfsExt4Parameters }} mkfs-ext4-parameters: {{ .Values.defaultSettings.mkfsExt4Parameters }}
disable-replica-rebuild: {{ .Values.defaultSettings.disableReplicaRebuild }} disable-replica-rebuild: {{ .Values.defaultSettings.disableReplicaRebuild }}
replica-replenishment-wait-interval: {{ .Values.defaultSettings.replicaReplenishmentWaitInterval }} replica-replenishment-wait-interval: {{ .Values.defaultSettings.replicaReplenishmentWaitInterval }}
concurrent-replica-rebuild-per-node-limit: {{ .Values.defaultSettings.concurrentReplicaRebuildPerNodeLimit }}
disable-revision-counter: {{ .Values.defaultSettings.disableRevisionCounter }} disable-revision-counter: {{ .Values.defaultSettings.disableRevisionCounter }}
system-managed-pods-image-pull-policy: {{ .Values.defaultSettings.systemManagedPodsImagePullPolicy }} system-managed-pods-image-pull-policy: {{ .Values.defaultSettings.systemManagedPodsImagePullPolicy }}
allow-volume-creation-with-degraded-availability: {{ .Values.defaultSettings.allowVolumeCreationWithDegradedAvailability }} allow-volume-creation-with-degraded-availability: {{ .Values.defaultSettings.allowVolumeCreationWithDegradedAvailability }}

View File

@ -100,6 +100,7 @@ defaultSettings:
mkfsExt4Parameters: ~ mkfsExt4Parameters: ~
disableReplicaRebuild: ~ disableReplicaRebuild: ~
replicaReplenishmentWaitInterval: ~ replicaReplenishmentWaitInterval: ~
concurrentReplicaRebuildPerNodeLimit: ~
disableRevisionCounter: ~ disableRevisionCounter: ~
systemManagedPodsImagePullPolicy: ~ systemManagedPodsImagePullPolicy: ~
allowVolumeCreationWithDegradedAvailability: ~ allowVolumeCreationWithDegradedAvailability: ~