SHOW REBALANCE STATUS

Shows the status of the currently executing REBALANCE PARTITIONS, RESTORE REDUNDANCY, RESTORE, ATTACH LEAF, auto-failover or auto-attach operation on a database.

Syntax

SHOW REBALANCE STATUS ON db_name

Remarks

  • db_name - name of a SingleStore database.

  • This command must be run on the master aggregator node (see Node Requirements for SingleStore Commands ).

  • SELECT * FROM information_schema.MV_REBALANCE_STATUS
    WHERE database_name = 'db_name';
  • Refer to the Permission Matrix for the required permission.

Example

Run the following command to rebalance partitions:

REBALANCE PARTITIONS ON mydb;

View the status of REBALANCE PARTITIONS while it is still running:

SHOW REBALANCE STATUS ON mydb;
+-----------------------------------+---------+-------------+-------------+-------+-----------+--------------+
| Action                            | Ordinal | Target_Host | Target_Port | Phase | Status    | Running_Time | 
+-----------------------------------+---------+-------------+-------------+-------+-----------+--------------+
| COPY PARTITION                    | 13      | 127.0.0.1   | 10002       | 3     | success   | 4009         | 
| COPY PARTITION                    | 2       | 127.0.0.1   | 10003       | 4     | success   | 5109         | 
| COPY PARTITION                    | 2       | 127.0.0.1   | 10004       | 4     | success   | 5112         | 
| PROMOTE PARTITION WITH DROP FORCE | 2       | 127.0.0.1   | 10003       | 5     | running   | 405          | 
| DROP PARTITION                    | 2       | 127.0.0.1   | 10002       | 6     | scheduled | NULL         | 
| DROP PARTITION                    | 13      | 127.0.0.1   | 10004       | 6     | scheduled | NULL         | 
+-----------------------------------+---------+-------------+-------------+-------+-----------+--------------+

Note: The Status column displays success for the activities that are already complete.

Last modified: January 9, 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