BOOTSTRAP AGGREGATOR

Promotes a node to Master Aggregator.

Syntax

BOOTSTRAP AGGREGATOR <host>;

Remarks

  • BOOTSTRAP AGGREGATOR creates a new cluster with this node as the master aggregator.

  • This command is required to install a SingleStore cluster without using management tools like sdb-admin, memsqlctl, or MemSQL Ops.

  • To set up a new cluster without using management tools, first run this command on one node to configure it as the master aggregator. Then, add each leaf node by running the ADD LEAF command on the master aggregator, and add each child aggregator by running the ADD AGGREGATOR command on the master aggregator.

  • When specifying the host, provide an address that can be used by other nodes to connect to the current node. The specified host must be accessible by every other node in the cluster. For example, use 192.168.0.1 instead of 127.0.0.1.

  • If BOOTSTRAP AGGREGATOR is called on an aggregator that is already joined to a cluster, it will fail with an error informing the caller that the aggregator is already joined to the cluster.

  • Always use stable addresses for optimal function with this command.

  • Refer to the Permission Matrix for the required permission.

Examples

The first example demonstrates how to bootstrap the cluster with the node hosted at 10.0.2.15 as the master aggregator. Note that the client is connected to the same node that is being bootstrapped:

BOOTSTRAP AGGREGATOR '10.0.2.15';
Query OK, 0 rows affected (1.55 sec)
SHOW AGGREGATORS;
+-----------+------+--------+--------------------+------------------------------+-------------------+
| Host      | Port | State  | Opened_Connections | Average_Roundtrip_Latency_ms | Master_Aggregator |
+-----------+------+--------+--------------------+------------------------------+-------------------+
| 10.0.2.15 | 3306 | online |                  1 |                         NULL |                 1 |
+-----------+------+--------+--------------------+------------------------------+-------------------+
1 row in set (0.00 sec)

Last modified: July 31, 2023

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