# SHOW REBALANCE STATUS

The `SHOW REBALANCE STATUS` command shows the status of the currently executing `REBALANCE PARTITIONS`, `RESTORE REDUNDANCY`, `RESTORE`, `ATTACH LEAF`, auto-failover or auto-attach operation on a database.

## Syntax

```sql
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](https://docs.singlestore.com/db/v9.0/reference/sql-reference/cluster-management-commands.md) ).
* Alternatively, you can query the information schema view `MV_REBALANCE_STATUS` . The following query returns the same output as the `SHOW REBALANCE STATUS ON db_name` command:
  ```sql
  SELECT * FROM information_schema.MV_REBALANCE_STATUS
  WHERE database_name = 'db_name';
  ```
* Refer to the [Permissions Matrix](https://docs.singlestore.com/db/v9.0/reference/sql-reference/security-management-commands/permissions-matrix.md) for the required permissions.

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.

## Estimated\_Time\_Remaining\_Ms

The `Estimated_Time_Remaining_Ms` column contains an estimate (in milliseconds) for each low-level command as follows:

* **Command is running**

  * The estimate is the remaining time for the command to complete.
  * For a running `COPY PARTITION` operation, the engine obtains the remaining-time estimate from the `ESTIMATED_CATCHUP_TIME_S` column in the [MV\_REPLICATION\_STATUS](https://docs.singlestore.com/db/v9.0/reference/information-schema-reference/replication-management/mv-replication-status.md) information schema view and converts it to milliseconds. For a running `PROMOTE` operation, the engine uses the larger of the catch-up estimate and the replay estimate. If the live estimates are not available, the value is `NULL`.
* **Command has not started**

  * The estimate is the expected runtime of the command.
  * For commands that have not started, `EXPLAIN REBALANCE`, and other action types (such as `DROP PARTITION`), SingleStore uses a per-database, per-action-type exponential moving average of previous completed runtimes. The latest measurement has a weight of 0.1, and the stored average has a weight of 0.9.

The estimate is based on historical runs for the same database and action type, and its accuracy depends on how well the previous runs reflect current conditions. It is not a confidence interval and does not automatically account for changes in data volume between infrequent rebalance operations.

## Example

Run the following command to rebalance partitions:

```sql
REBALANCE PARTITIONS ON mydb;
```

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

```sql
SHOW REBALANCE STATUS ON mydb;

```

```output

+-----------------------------------+---------+-------------+-------------+-------+-----------+--------------+-----------------------------+
| Action                            | Ordinal | Target_Host | Target_Port | Phase | Status    | Running_Time | Estimated_Time_Remaining_Ms |
+-----------------------------------+---------+-------------+-------------+-------+-----------+--------------+-----------------------------+
| COPY PARTITION                    | 13      | 127.0.0.1   | 10002       | 3     | success   | 4009         | 0                           |
| COPY PARTITION                    | 2       | 127.0.0.1   | 10003       | 4     | success   | 5109         | 0                           |
| COPY PARTITION                    | 2       | 127.0.0.1   | 10004       | 4     | success   | 5112         | 0                           |
| PROMOTE PARTITION WITH DROP FORCE | 2       | 127.0.0.1   | 10003       | 5     | running   | 405          | 1130                        |
| DROP PARTITION                    | 2       | 127.0.0.1   | 10002       | 6     | scheduled | NULL         | 1002                        |
| DROP PARTITION                    | 13      | 127.0.0.1   | 10004       | 6     | scheduled | NULL         | 1002                        |
+-----------------------------------+---------+-------------+-------------+-------+-----------+--------------+-----------------------------+
```

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

***

Modified at: October 16, 2026

Source: [/db/v9.0/reference/sql-reference/cluster-management-commands/show-rebalance-status/](https://docs.singlestore.com/db/v9.0/reference/sql-reference/cluster-management-commands/show-rebalance-status/)

(An index of the documentation is available at /llms.txt)