lbcli restart node-instance

AI Tools

Restarts a running node instance (Tech Preview).

Synopsis

Restarts a running node instance (Tech Preview).

Restarts a specific node instance's Lightbits services/instances.

This includes the duroslight service and the node management instance of the specified node.

To also restart the backend, specify --consider-backend=true (the default is false).

This is useful for dual-node servers where you want to restart a single node instance without affecting the other node or if you just want to restart the duroslight.

This operation will be blocked if it could cause data unavailability. Use --force to override this check.

Warning!

This is a potentially disruptive operation that should be used with care. Only system administrators can execute this command.

Note that node maintenance operations (stop/start/restart) are a tech preview, for evaluative purposes only and API syntax might change. They should not be used in production clusters.

lbcli restart node-instance [flags]

Examples:

# Restart a node instance with UUID a1b2c3d4-e5f6-7890-abcd-ef1234567890 lbcli -J $JWT restart node-instance --node-uuid=a1b2c3d4-e5f6-7890-abcd-ef1234567890 # Force restart a node instance even if volumes may become unavailable lbcli -J $JWT restart node-instance --node-uuid=a1b2c3d4-e5f6-7890-abcd-ef1234567890 --force # Restart a node instance without the backend (duroslight and control plane only) lbcli -J $JWT restart node-instance --node-uuid=a1b2c3d4-e5f6-7890-abcd-ef1234567890 --consider-backend=false

Flag	Short	Type	Description
--help	-h	bool	Help for `node-instance`.
--node-uuid		string	The UUID of the node instance to restart (required).
--force		bool	Force a restart even if volumes could become unavailable (default: false).
--consider-backend		bool	Whether to include the backend instance in the operation (default: false).

Last updated on

Was this page helpful?