lbcli stop node-instance

Stops a running node instance (Tech Preview).

Synopsis

This operation stops a specific node instance, stopping all of the node's Lightbits services, including duroslight and the backend instance.

This is useful for dual-node servers where you want to stop a single node instance without affecting the other node.

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

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. They should not be used in production clusters.

Bash
    
 
lbcli stop node-instance [flags]
Copy

Examples:

Bash
    
​x
 
# Stop a node instance with UUID a1b2c3d4-e5f6-7890-abcd-ef1234567890lbcli -J $JWT stop node-instance --node-uuid=a1b2c3d4-e5f6-7890-abcd-ef1234567890​# Force stop a node instance even if volumes may become unavailablelbcli -J $JWT stop node-instance --node-uuid=a1b2c3d4-e5f6-7890-abcd-ef1234567890 --force
Copy

Flag	Short	Type	Description
--help	-h	bool	Help for `node-instance`.
--node-uuid		string	The UUID of the node instance to stop (required).
--force		bool	Force stop even if volumes could become unavailable (default: false).

Last updated on

Was this page helpful?