MEMSQL-STOP
On this page
Stops a SingleStoreDB node given a SingleStoreDB node ID.
Usage
usage: memsql-ops memsql-stop [--settings-file SETTINGS_FILE] [--async][--all] [--no-prompt] [--hard-stop][--timeout TIMEOUT][memsql_id]Stop a SingleStoreDB node.positional arguments:memsql_id The ID of the SingleStoreDB node to stop.optional arguments:--settings-file SETTINGS_FILEA path to a MemSQL Ops settings.conf file. If not set,we will use the file in the same directory as theMemSQL Ops binary.--async If this option is true, we will exit without waitingfor SingleStoreDB to be fully stopped.--all Stop all SingleStoreDB nodes in the cluster.--no-prompt Skip interactive prompts if ID is not provided. Thisshould be used for non-interactive scripts andautomation.--hard-stop If true, we will kill the SingleStoreDB process instead ofstopping it.--timeout TIMEOUT Number of seconds to wait for the SingleStoreDB nodes tostop. The default is 300 seconds.
Notes
When stopping a leaf, you should detach it from the cluster first to avoid possibly losing unreplicated data in asynchronous replication mode on that leaf.
Stopping the master aggregator will leave your cluster without a master aggregator.
If aggregator_
is set to ON
, stopping half or more of the aggregators will cause the other aggregators to stop.aggregator_
to OFF
before stopping the aggregators, and set it back to ON
after restarting the aggregators.
Last modified: April 25, 2023