Outdated Version

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

unregister-node

Info

SingleStore Managed Service does not support this command.

Unregister a SingleStoreDB node on a specific host.

Usage

Unregister a SingleStoreDB node on a specific host.

This command will perform the following actions on the SingleStoreDB node(s):
- unregister the node(s) in Toolbox and memsqlctl

It will NOT:
- `REMOVE <LEAF|AGGREGATOR>` from the Master Aggregator
- stop the node if it is running
- delete any node-related directories (data, auditlogs, plancache, tracelogs, etc.)
- 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)

Usage:
  sdb-admin unregister-node [flags]

Flags:
  -a, --all                  Unregister all nodes in the cluster
      --all-on-host string   Unregister all nodes on a specific host
  -h, --help                 Help for unregister-node
      --memsql-id MemsqlID   The node ID of the node to unregister

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 the --yes or --json flags to override interactive behavior.