Database Clusters

This section describes on how to troubleshoot the database cluster. It can be a new deployment, import a cluster or the existing database cluster managed by ClusterControl.

New deployment abd import cluster

The new deployment of database cluster through ClusterControl will trigger a new job either it is succesfull or failed. How to check if the deployment of new cluster is failed and what is the reason of the failed can be checked in the jobs.

ClusterControl GUIClusterControl CLI

In the ClusterControl UI, go to Activity Center → Jobs, check the failed jobs for the deployment cluster.
There is an Action menu in the jobs, expand the details for detailed errors.

Check the history of the job
```
s9s jobs --list --show-failed
```
Dig the detailed error of failed job
```
s9s job --log --job-id=<value>
```

The job-id can be found from the job list output above.

Existing database cluster

Failure can occur in the database cluster due to various reasons. It may stem from issues in the network, disk failures, or problems within the operating system itself. It is important to know how to monitor and assess what is happening within the database cluster.

Below are steps to check the database cluster in ClusterControl.

ClusterControl GUIClusterControl CLI

In the ClusterControl UI, go to Home page of ClusterControl, it will shown what cluster and nodes that is degraded.
Go to the failure Cluster, check the triggered Alarm under the Alarm.
If the failure are related to the database, check the database log under the Logs → System Logs

Run the following command in ClusterControl host. The cluster list give information about the list of the cluster including the state (STARTED, FAILURE, UNKNOWN).
```
s9s cluster --list --long
```
The node list show information of which node that is failure in the cluster.
```
s9s nodes --list --cluster-id=<clusterId>
```
The clusterId value can be found when executing the cluster list command.
Check the triggered alarm in the CLI.
```
s9s alarm --list  --long
```