start-node

Description

Start one or all nodes on the host.

If neither --memsql-id nor --all is specified, memsqlctl will prompt the user to select a node from a table.

Usage

Usage:
  memsqlctl start-node [flags]

Flags:
  -a, --all                                        Start all nodes on the host
      --disable-auto-restart                       Disable automatic restart of memsqld on error
  -h, --help                                       Help for start-node
      --memsql-id strings                          The node ID of the node to start
  -r, --role {master, aggregator, leaf, unknown}   Only start nodes with this role (default Unspecified)

Global Flags:
  -c, --config FILE_PATH                     Path to the memsqctl config file
      --default-install-dir DIRECTORY_PATH   Path to the default install directory
      --insecure-ssl                         Fall back to insecure SSL connections to local nodes if memsqlctl is unable to otherwise establish a connection (ADVANCED)
  -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                     The path to the CA certificate file (in PEM format) to authenticate the database certificate
      --timeout duration                     Maximum time for operation to complete (e.g., 30s, 10m, 1.5h)
      --verbose-json                         Print output in JSON format, include some warnings and user messages
  -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

Remarks

  • This command is interactive unless you use either --yes or --json flag to override interactive behavior.

  • The memsqlctl start-node command is equivalent to the sdb-admin start-node command.

Output

The following is the standard output for the start-node command.

sudo memsqlctl start-node
+-------+------------+--------+------+---------------+---------+
| Index | MemSQL ID  |  Role  | Port | Process State | Version |
+-------+------------+--------+------+---------------+---------+
| 1     | 179062CAEE | Master | 3306 | Running       | 6.5.10  |
| 2     | E31F8D60BA | Leaf   | 3307 | Stopped       | 6.5.10  |
| 3     | All Nodes  |        |      |               |         |
+-------+------------+--------+------+---------------+---------+
Select an option: 2
memsqlctl will perform the following actions:
  · Set up runtime environment

  · Start node with MemSQL ID E31F8D60BA422D0DC1C82C0BE274C7DC51F6A754 on port 3307

Would you like to continue? [y/N]: y
✓ Set up runtime environment
✓ Started node with MemSQL ID E31F8D60BA422D0DC1C82C0BE274C7DC51F6A754 (1/1)
✓ Started 1 SingleStore nodes

Last modified: April 22, 2024

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK