lbcli get cluster-config (2.2 and above)

AI Tools

Gets cluster-config information.

lbcli get cluster-config [flags]

Examples:

# Get cluster-config info by provided config parameter name" lbcli -J $JWT get cluster-config --parameter=DurationToTurnIntoPermanentFailure

Flag	Short	Type	Default	Description
--help	-h	bool		Help for cluster-config.
--parameter		string		The cluster config parameter name. DurationToTurnIntoPermanentFailure - The threshold in seconds for determining that a node has permanently failed (the default is 4h). Example: 1h0m0s VolumeDeletionFromNodeDelay (for internal use) - Example: 15s ClusterName - The cluster name. 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. Example: 24h0m0s DeviceHealthIntervalForRaisingEvent - NVMe SSD failed device events suppression mechanism. Specify the time interval to raise a new event if the NVMe SSD device remains unhealthy. 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 a specified time window (the default is set to 2; a 0 value will disable the feature). RevivesWindowDuration: The time window to monitor the number of auto revive attempts (the default is set to 2 hours).

Flag

Short

Type

Default

Description

--help

-h

bool

Help for cluster-config.

--parameter

string

The cluster config parameter name.

DurationToTurnIntoPermanentFailure - The threshold in seconds for determining that a node has permanently failed (the default is 4h). Example: 1h0m0s
VolumeDeletionFromNodeDelay (for internal use) - Example: 15s
ClusterName - The cluster name.
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. Example: 24h0m0s
DeviceHealthIntervalForRaisingEvent - NVMe SSD failed device events suppression mechanism. Specify the time interval to raise a new event if the NVMe SSD device remains unhealthy. 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 a specified time window (the default is set to 2; a 0 value will disable the feature).
RevivesWindowDuration: The time window to monitor the number of auto revive attempts (the default is set to 2 hours).

This command returns the following fields for each snapshot. The default output format is human-readable. The human-readable output only shows some of these fields. The json/yaml output format is also supported and includes additional fields.

Field	Type	Description
name	string	Specify the name of the parameter to update: ClusterName [name]/ ClockDriftIntervalForRaisingEvent [time]/ DeviceHealthIntervalForRaisingEvent [time]/ DurationToTurnIntoPermanentFailure [time]/ PermanentFailureNoProgressTimeout [time]/ PermanentFailureRecheckInterval [time]/ VolumeDeletionFromNodeDelay [time]/ DefaultQoSName [string]/ AllowedNumRevives [int] DisableVolumeStatisticsExport [bool]/ EnableTrim [bool]/ EvictionNoProgressTimeout [time]/ RevivesWindowDuration [time]/ PgCleanupInterval [time]/ PgCleanupMaxDeletionsPerRun [int]/ PgCleanupStartMargin [int].
value	string	The value of the cluster config parameter, where the specific units are specific to the specified parameter.

Last updated on

Was this page helpful?