Watch the 7.3 Webinar On-Demand
This new release brings updates to Universal Storage, query
optimization, and usability that you won’t want to miss.
Please follow this guide to learn how to migrate to SingleStore tools.
SingleStore Managed Service does not support this command.
Deploy a SingleStore DB node (master aggregator, child aggregator or leaf) into a specific host where MemSQL Ops is installed.
If you are using memsql-deploy
to create a new cluster with MemSQL Ops, you cannot use the --license
flag with a license obtained through the SingleStore Customer Portal. Instead, set the --developer-edition
flag to deploy the cluster and then follow the steps listed in Setting or Replacing a License (MemSQL Ops) to either set your license in the MemSQL Ops UI or through the memsql-ops
CLI.
usage: memsql-ops memsql-deploy [--settings-file SETTINGS_FILE] [--async]
[-a AGENT_ID] [-r {leaf,aggregator,master}]
[-P PORT] [-L LICENSE | --developer-edition]
[--version-hash VERSION_HASH]
[--redundancy-level {1,2}]
[--availability-group {1,2}]
Deploy a SingleStore DB node.
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 SingleStore DB to be fully deployed.
-a AGENT_ID, --agent-id AGENT_ID
The MemSQL Ops agent ID to use. Defaults to the
locally running agent if available.
-r {leaf,aggregator,master}, --role {leaf,aggregator,master}
The role of the SingleStore DB node.
-P PORT, --port PORT The port to use for this SingleStore DB node.
-L LICENSE, --license LICENSE
The license key to use.
--developer-edition Whether or not to use the Developer Edition of SingleStore DB.
--version-hash VERSION_HASH
A SingleStore DB version hash to use.
--redundancy-level {1,2}
What redundancy level to run this SingleStore DB node in. This
is only applicable when deploying a master aggregator
and it is only available to users with Enterprise
licenses.
--availability-group {1,2}
Which availability group to run this SingleStore DB node in.
This is only applicable when deploying a leaf node and
it is only available to users with Enterprise
licenses.