Outdated Version

You are viewing an older version of this section. View current production version.

delete-node

Info

MemSQL Helios does not support this command.

Delete a SingleStoreDB node on a specific host.

Usage

Delete a SingleStoreDB node on a specific host.

This command will perform the following actions on the SingleStoreDB 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 delete all data, delete all nodes, uninstall all `singlestoredb-server` packages, and unregister all SingleStoreDB hosts, use `sdb-deploy destroy-cluster` (e.g., to destroy the existing cluster and deploy a new one).

Usage:
  sdb-admin delete-node [flags]

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

  • A node must be stopped before it can be deleted. Use the stop-node command to perform this action.
  • Starting from singlestoredb-toolbox version 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.
  • 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).
  • This command is interactive unless you use either the --yes or --json flags to override interactive behavior.