Outdated Version

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


MemSQL Ops has been deprecated

Please follow this guide to learn how to migrate to SingleStore tools.

Available since MemSQL Ops version 4.0.31.

Update the root password for a MemSQL node.


usage: memsql-ops memsql-update-root-password [--settings-file SETTINGS_FILE]
                                              [--async] [--no-prompt]
                                              [-p [PASSWORD]]
                                              [--no-confirmation] [--force]

Update the root password for a MemSQL node.

positional arguments:
  memsql_id             The ID of the MemSQL 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 MemSQL Ops to finish updating the root password.
  --no-prompt           Skip interactive prompts if ID is not provided. This
                        should be used for non-interactive scripts and
  -p [PASSWORD], --password [PASSWORD]
                        The password to use for the root user on the MemSQL
                        node. Leave blank to read the MEMSQL_PASSWORD
                        environment variable, or have a password prompt if
                        MEMSQL_PASSWORD is not set. Note: empty string value
                        clears the password for root.
  --no-confirmation     If this option is specified, we will update the root
                        password without prompting for confirmation.
  --force               If this is true, we will set the password in MemSQL
                        Ops even if we cannot currently connect to MemSQL.


  • memsql-update-root-password is an offline operation.
  • Before running memsql-update-root-password ensure there are no orphan partitions in the cluster. See Understanding Orphaned Partitions for detecting and resolving orphan partitions.
  • In a cluster configured for high availability, you should run REBALANCE PARTITIONS on each database from the master aggregator after running memsql-update-root-password. If updating the root password of multiple leaf nodes using memsql-update-root-password you may run REBALANCE PARTITIONS from the master aggregator after all leaf node root passwords have been updated.