SHOW LEAVES

Shows the leaves in a cluster.

Syntax

SHOW LEAVES;

Output

Column

Description

Host

Host name or IP address

Port

Port number

Availability_Group

Availability group to which this leaf belongs

Pair_Host

Pair host

Pair_Port

Pair port

State

Leaf state (see Leaf States)

Opened_Connections

Number of opened connections

Average_Roundtrip_Latency_ms

Average round-trip latency in milliseconds, calculated as SELECT 1 from the master aggregator to the leaf

NodeId

The unique ID of a given leaf node.

Grace_Period_in_Seconds

Time left for the node to recover after failing and coming back online. This is set by engine variable failover_initial_grace_interval_seconds

Minimum_Pre_Prepare_Ts

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

Runtime_State

Internal

Remarks

Example

SHOW LEAVES;
+---------------+-------+--------------------+---------------+-----------+--------+--------------------+------------------------------+
| Host          | Port  | Availability_Group | Pair_Host     | Pair_Port | State  | Opened_Connections | Average_Roundtrip_Latency_ms |
+---------------+-------+--------------------+---------------+-----------+--------+--------------------+------------------------------+
| 192.168.1.110 |  3306 |                  1 | 192.168.1.112 |      3306 | online |                  5 |                     0.299    |
| 192.168.1.111 |  3306 |                  1 | 192.168.1.113 |      3306 | online |                  5 |                     0.293    |
| 192.168.1.112 |  3306 |                  2 | 192.168.1.110 |      3306 | online |                  1 |                     0.271    |
| 192.168.1.113 |  3306 |                  2 | 192.168.1.111 |      3306 | online |                  1 |                     0.264    |
+---------------+-------+--------------------+---------------+-----------+--------+--------------------+------------------------------+
4 rows 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