You are viewing an older version of this section. View current production version.
Enable high availability.
Enable high availability Usage: memsqlctl enable-high-availability [flags] Flags: -h, --help Help for enable-high-availability -p, --password STRING The MemSQL user's password for re-adding the leaves --skip-colocate-check Do not check whether the colocation of a leaf pair is necessary --skip-disk-check Do not check that each leaf node's host has at least half of its disk space free --user string The MemSQL user for re-adding the leaves (default "root") Global Flags: -c, --config FILE_PATH Path to the memsqctl config file --default-install-dir DIRECTORY_PATH Path to the default install directory -j, --json Print output in JSON format --node-metadata-file FILE_PATH Path to the node metadata file --parallelism POSITIVE_INTEGER Maximum amount of operations to be run in parallel --ssl-ca FILE_PATH Path to the CA certificate file in PEM format to authenticate the MemSQL server certificate --timeout duration Maximum time for operation to complete (e.g., 30s, 10m, 1.5h) -v, --verbosity count Increase logging verbosity -y, --yes Enable non-interactive mode and assume the user would like to move forward with the proposed actions by default
Must be run on a host containing a running and connectable master aggregator.
This command connects to the master aggregator, sets
redundancy_level to 2, and then removes and re-adds half of the leaf nodes in the cluster into the second availability group.
This command will only work if all leaf nodes in the cluster share a user and password with the
This command is offline and will interrupt the currently running workload. It is best to run this command before adding any leaf nodes to the cluster.
This command is interactive unless you use either the
--json flags to override interactive behavior.
memsqlctl enable-high-availability command is equivalent to the memsql-admin enable-high-availability command.