# 5. Are there other ongoing operational activities?

The next step in troubleshooting your cluster is checking other ongoing operational activities that may be affecting your cluster performance.

1. Navigate to the Active Queries page in Studio from the master aggregator, or query [MV\_PROCESSLIST](https://docs.singlestore.com/db/v9.1/reference/information-schema-reference/query-performance-workload-management-and-statistics/mv-processlist.md)
   ```sql
   SELECT * FROM information_schema.mv_processlist;
   ```

2. Search (ctrl-F) in the Active Queries page, or look in the results of your query to `MV_PROCESSLIST` for any of the following: `ALTER, CREATE, DROP, ADD|REMOVE LEAF/AGGREGATOR, BACKUP/RESTORE, REBALANCE, RESTORE REDUNDANCY`.

3. For either the Active Queries page, or `MV_PROCESSLIST`, check the `status` column to see if any of these activities are long running, or waiting on other operations.

   * If an operation is `waiting on metadata lock`, the query is likely waiting on a cluster wide operation such as a backup.

## Next Steps

* If no other ongoing operational activities were identified: continue to [Step 6](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/6-checking-node-partition-and-overall-database-health.md).

***

Modified at: July 17, 2024

Source: [/db/v9.1/user-and-cluster-administration/troubleshooting/5-are-there-other-ongoing-operational-activities/](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/5-are-there-other-ongoing-operational-activities/)

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