ADD AGGREGATOR

Adds a new child aggregator to a cluster.

Syntax

ADD AGGREGATOR user[:'password']@'host':port;

Remarks

  • This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStore Commands ).

  • The specified user account must have full permissions on the node to execute this command, namely the cluster privilege. For more information, see Permissions Matrix.

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

  • This command causes implicit commits. Refer to COMMIT for more information.

  • See the Permission Matrix for the required permission.

Example

The following example demonstrates how to add a child aggregator to a cluster. Note that the client is connected to the master aggregator:

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)
ADD AGGREGATOR root@'10.0.2.16':3306;
SHOW AGGREGATORS;
+-----------+------+--------+--------------------+------------------------------+-------------------+
| Host      | Port | State  | Opened_Connections | Average_Roundtrip_Latency_ms | Master_Aggregator |
+-----------+------+--------+--------------------+------------------------------+-------------------+
| 10.0.2.15 | 3306 | online |                  1 |                         NULL |                 1 |
| 10.0.2.16 | 3306 | online |                  0 |                        0.218 |                 0 |
+-----------+------+--------+--------------------+------------------------------+-------------------+
2 rows in set (0.00 sec)

Last modified: August 3, 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