Please follow this guide to learn how to migrate to MemSQL tools.
Stops a MemSQL node given a MemSQL node ID.
usage: memsql-ops memsql-stop [--settings-file SETTINGS_FILE] [--async] [--all] [--no-prompt] [--hard-stop] [--timeout TIMEOUT] [memsql_id] Stop a MemSQL node. positional arguments: memsql_id The ID of the MemSQL node to stop. optional arguments: --settings-file SETTINGS_FILE A path to a MemSQL Ops settings.conf file. If not set, we will use the file in the same directory as the MemSQL Ops binary. --async If this option is true, we will exit without waiting for MemSQL to be fully stopped. --all Stop all MemSQL nodes in the cluster. --no-prompt Skip interactive prompts if ID is not provided. This should be used for non-interactive scripts and automation. --hard-stop If true, we will kill the MemSQL process instead of stopping it. --timeout TIMEOUT Number of seconds to wait for the MemSQL nodes to stop. The default is 300 seconds.
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. See DETACH LEAF for more information on this command.
Stopping the master aggregator will leave your cluster without a master aggregator. A master aggregator is required to handle automatic partition failover and DDL operations. Thus, if you plan on stopping the master aggregator for an extended period of time, you should promote another aggregator to master aggregator to preserve availability of all services. See AGGREGATOR SET AS MASTER for more information on this command.
aggregator_failure_detection is set to
ON, stopping half or more of the aggregators will cause the other aggregators to stop. Aggregator failure detection is meant to protect data integrity in case of network partitions and is on by default. However, if you stop half of the aggregators and want to keep the other half online, set the global variable
OFF before stopping the aggregators, and set it back to
ON after restarting the aggregators.