Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

AGGREGATORS

This view contains information about aggregators. It is useful for understanding the number and attributes of the aggregators for a given cluster.

Column Name

Description

HOST

The hostname or IP address for the related aggregator.

PORT

The port number of the related aggregator.

STATE

The current state of a given aggregator.

OPENED_CONNECTIONS

The number of connections opened on a given aggregator.

AVERAGE_ROUNDTRIP_LATENCY

The average ping roundtrip latency in milliseconds for a given aggregator.

MASTER_AGGREGATOR

If a given aggregator is in the role of master, this will be 1, otherwise 0.

ROLE

Whether a given aggregator is a master or child. This will be leader for master aggregators, and follower for children.

NODE_ID

The unique ID of a given aggregator node.

LOCAL_MINIMUM_PRE_PREPARE_TS

The timestamp of the coordinator's oldest distributed transaction.

MINIMUM_PRE_PREPARE_TS

The timestamp of the cluster-wide oldest distributed transaction among all participants (master aggregator and leaves).

RUNTIME_STATE

Internal.

AVAILABILITY_GROUP

The ID of the availability group to which the aggregator belongs.

Last modified:

Was this article helpful?

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In