lbcli update cluster-config (2.2 and above)

AI Tools

Updates cluster-config parameter.

lbcli update cluster-config [flags][flags]

Examples:

lbcli -J $JWT update cluster-config --parameter=DurationToTurnIntoPermanentFailure --value=20m lbcli -J $JWT update cluster-config --parameter=PermanentFailureNoProgressTimeout --value=1h lbcli -J $JWT update cluster-config --parameter=PermanentFailureRecheckInterval --value=10m lbcli -J $JWT update cluster-config --parameter=VolumeDeletionFromNodeDelay --value=30s lbcli -J $JWT update cluster-config --parameter=ClusterName --value=cluster1 lbcli -J $JWT update cluster-config --parameter=EnableTrim --value=true lbcli -J $JWT update cluster-config --parameter=ClockDriftIntervalForRaisingEvent --value=24h lbcli -J $JWT update cluster-config --parameter=DisableVolumeStatisticsExport --value=true lbcli -J $JWT update cluster-config --parameter=DEKsRetentionPeriod --value=168h

Flag

Short

Type

Default

Description

--help

-h

bool


Help for cluster-config.

--parameter/value


string


Parameter: The cluster config parameter name.

Value: The cluster config parameter value to update for the parameter.

  • DurationToTurnIntoPermanentFailure - The threshold in seconds for determining that a node has permanently failed. Default value: 4h; minimum value: 1h; maximum value: 256h. Example: 2h0m0s

  • VolumeDeletionFromNodeDelay (for internal use). Minimum value: 5s.; maximum value: 2m. Example: 30s

  • ClusterName - The cluster name. This should not be empty, and should adhere to the regx name rule.

  • ClockDriftIntervalForRaisingEvent - Clock drift events suppression mechanism. Specify the time interval to raise a new event if the clock drift between cluster servers is still detected. Minimum value: 30m; maximum value: 256y. Example: 24h

  • DeviceHealthIntervalForRaisingEvent - NVMe SSD failed device events suppression mechanism. Specify the time interval to raise a new event if the NVMe SSD device remains unhealthy. Minimum value: 30m; maximum value: 256y. Example: 24h0m0s

  • DefaultQoSName - The default QoS policy of the cluster (to be used when neither volume or project have a QoS policy specified). Example: silver-policy

  • AllowedNumRevives - The number of attempts to revive services in specified time window (the default is set to 2. A 0 value will disable the feature). Maximum value: 64.

  • RevivesWindowDuration - The time window to monitor the number of auto revive attempts (the default is set to 2 hours). Minimum value: 1h; Maximum value: 1week.