Sign inTry Free

EXPLAIN REBALANCE ALL DATABASES

On this page

The EXPLAIN REBALANCE ALL DATABASES command returns the set of steps that REBALANCE ALL DATABASES would run if you run it at that time.

Syntax

EXPLAIN REBALANCE ALL DATABASES;

Example

EXPLAIN REBALANCE ALL DATABASES;
+----------+-----------------------------+---------+-------------+-------------+-------+-----------------------------+
| Database | Action                      | Ordinal | Target_Host | Target_Port | Phase | Estimated_Time_Remaining_Ms |
+----------+-----------------------------+---------+-------------+-------------+-------+-----------------------------+
| x_db     | COPY PARTITION              | 13      | 127.0.0.1   | 10002       | 3     | 7821                        |
| x_db     | COPY PARTITION              | 2       | 127.0.0.1   | 10003       | 4     | 7821                        |
| x_db     | COPY PARTITION              | 2       | 127.0.0.1   | 10004       | 4     | 7821                        |
| x_db     | PROMOTE PARTITION WITH DROP | 2       | 127.0.0.1   | 10003       | 5     | 1351                        |
| x_db     | DROP PARTITION              | 2       | 127.0.0.1   | 10002       | 6     | 1002                        |
| x_db     | DROP PARTITION              | 13      | 127.0.0.1   | 10004       | 6     | 1002                        |
+----------+-----------------------------+---------+-------------+-------------+-------+-----------------------------+

Note: The Estimated_Time_Remaining_Ms is the estimated total time (in milliseconds) that each low-level command will take to complete.

The Ordinal is the target partition’s ordinal, and the Target_Host and Target_Port correspond to the destination leaf. Any two operations in the same Phase can be run in parallel and phases are run in order. For example, the aggregator can run COPY PARTITION on partitions test:1 and test:3 in parallel. The exact meaning of what each phase means is arbitrary and depends on the particular rebalance operation. The Estimated_Time_Remaining_Ms is the estimated total time (in milliseconds) that each low-level command will take to complete.

Last modified:

Was this article helpful?

On this page

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