shc cluster rm
shc cluster rm
Section titled “shc cluster rm”remove a node from the cluster
Synopsis
Section titled “Synopsis”Remove another node from the cluster (daemon-side DELETE /api/method/shc.cluster.rm). Self-removal (this node leaving) belongs to shc cluster leave.
Refuses while deployment rows still name the node (X400017NODDEP). Relocate them with shc node drain <node> first: it moves every deployment bound to the node, running or stopped. Clear anything it still leaves behind with shc uninstall <stack>.
--force skips that refusal only. The rows are not evicted or moved: they are left naming the removed node. The quorum floor is never bypassable.
The voter count follows the control-plane fence: after a voter is removed the suffrage pass promotes a non-voter inside the fence within a minute or two. --rebalance promotes it first instead, so the set goes 3->4->3 and never dips below target.
A --rebalance that fails part-way is a hard stop: the named voter is not removed and the voter set is unchanged, so re-running the same command resumes from where it stopped.
Once the daemon has the request it finishes the removal even if this command is interrupted or loses its connection, and shc node ls shows the result.
shc cluster rm <node> [flags]Options
Section titled “Options” -f, --force remove the node even though deployment rows still name it; those rows are left naming a node that is gone (nothing is evicted or moved) -h, --help help for rm --rebalance promote a non-voter inside the control-plane fence before removing the named voter, so the cluster never dips below its voter target; refuses if there is none to promote -y, --yes skip confirmation promptOptions inherited from parent commands
Section titled “Options inherited from parent commands” --config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win -d, --debug enable debug mode (default: $SHC_DEBUG) -e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default") --exclude string comma-separated dotted paths to drop --fields string comma-separated columns/keys to show (and their order) --filter string comma-separated dotted paths to keep (drops everything else) -o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT) -s, --stack string stack name (default: $SHC_STACK) -t, --tenant string tenant name (default: $SHC_TENANT) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc cluster - manage cluster nodes and membership