delete-node

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

Description

Completely removes a node and its data from a host.

This command removes the specified node from the cluster and deletes its data. If the node is a leaf node, this command will also rebalance the leaf node’s partitions into the remaining cluster.

To remove a leaf node from the cluster without deleting its data, and with the ability to add it back to the cluster, refer to the sdb-admin remove-leaf command.

A node must be stopped before it can be deleted. Use the stop-node command to perform this action.

Before deleting a leaf node, sdb-admin delete-node runs the remove-leaf command to remove it from the cluster. Removing the leaf node transfers its data to other leaves in the cluster and prevents data loss (in case HA is not enabled).

As of Toolbox 1.2.2, sdb-admin delete-node removes all the data on the node and deletes the node’s record from the node metadata file, nodes.hcl.

Note that this action is only reversible by deploying a new leaf in the same location, attaching it, and rebalancing partitions.

This command will perform the following actions on the specified node(s):

REMOVE <LEAF|AGGREGATOR> from the Master Aggregator
Delete all the node-related directories (data, auditlogs, plancache, tracelogs, etc.)

It will not:

Uninstall singlestoredb-server from the host (use sdb-deploy uninstall to do so)
Unregister the host from Toolbox (use sdb-toolbox-config unregister-host to do so)

To destroy the existing cluster by deleting all data, deleting all nodes, uninstalling all singlestoredb-server packages, and unregistering all hosts so a new cluster can be deployed, use sdb-deploy destroy-cluster.

Usage

Usage:
  sdb-admin delete-node [flags]

  For flags that can accept multiple values (indicated by VALUES after the name of the flag),
  separate each value with a comma.

Flags:
  -a, --all                  Delete all nodes in the cluster
  -h, --help                 Help for delete-node
      --memsql-id MemsqlID   The node ID of the node to delete
      --skip-remove          Skip removing the leaves and aggregators
      --stop                 Stop each node before deletion

Global Flags:
      --backup-cache FILE_PATH                File path for the backup cache
      --cache-file FILE_PATH                  File path for the Toolbox node cache
  -c, --config FILE_PATH                      File path for the Toolbox configuration
      --disable-colors                        Disable color output in console, which some terminal sessions/environments may have difficulty with
      --disable-spinner                       Disable the progress spinner, which some terminal sessions/environments may have issues with
  -j, --json                                  Enable JSON output
      --parallelism POSITIVE_INTEGER          Maximum number of operations to run in parallel
      --runtime-dir DIRECTORY_PATH            Where to store Toolbox runtime data
      --ssh-control-persist SECONDS           Enable SSH ControlPersist and set it to the specified duration in seconds
      --ssh-max-sessions POSITIVE_INTEGER     Maximum number of SSH sessions to open per host, must be at least 3
      --ssh-strict-host-key-checking          Enable strict host key checking for SSH connections
      --ssh-user-known-hosts-file FILE_PATH   Path to the user known_hosts file for SSH connections. If not set, /dev/null will be used
      --state-file FILE_PATH                  Toolbox state file path
  -v, --verbosity count                       Increase logging verbosity: valid values are 1, 2, 3. Usage -v=count or --verbosity=count
  -y, --yes                                   Enable non-interactive mode and assume the user would like to move forward with the proposed actions by default

Remarks

This command is interactive unless you use either --yes or --json flag to override interactive behavior.