Check the cluster status

You can check the cluster status by using OceanBase Cloud Platform (OCP) or SQL statements.

Check the cluster status

Check the cluster status in OCP

1. Log on to the OCP console. The Cluster Overview page appears.

2. In the Clusters list on the Cluster Overview page, find the target cluster and click its name.

3. In the left-side navigation pane of the page that appears, click Health Inspection.

4. In the Inspection Results area, view the status of the current cluster.

5. Click Export Inspection Report in the upper-right corner of the Health Inspection page. Then, view the exported inspection results.

   Note

   Inspection reports display the content in the Inspection Results section in the .html format.

   The following table describes the parameters displayed in the inspection results.

   Parameter	Description
   Module	The object on which the inspection is performed. Valid values: Cluster, Host, OB_SEVER, and OB_PROXY.
   Metric	The metric of the cluster, host, OBServer node, or ODP. For more information, see the following Inspection metrics table.
   Health Status	The health status of the object. Valid values: Critical, Warning, and Healthy.
   Result Description	The detailed inspection result of the object, such as the information about the host, cluster, ODP, zone, or OBServer node.
   Inspected At	The time when the inspection was initiated. Example: 17:04:00 on November 27, 2020.

   You can check the status of a cluster based on the metrics displayed by the Metric parameter. The following table describes the cluster metrics.

   Inspection metric	Sub-metric	Sample result
   Cluster status	operation status: the O&M status of the cluster. compaction status: the compaction status of the cluster.	O&M: The cluster is running and healthy. Compaction: The cluster is not undergoing compaction and is healthy.
   Zone status	compaction status: the compaction status of the zone. operation status: the O&M status of the zone.	O&M status: zone: zone1 zone status: creating, alert zone: zone2 zone status: running, healthy Compaction status: zone: zone1 zone status: not in compaction, healthy zone: zone2 zone status: in compaction, alert
   Alert	Stopped event count: the number of stopped-level alerts. Critical event count: the number of critical-level alerts. Warning event count: the number of warning-level alerts. Caution event count: the number of caution-level alerts. Reminder event count: the number of reminder-level alerts.	Number of stopped-level alerts: 1, > 0, critical Number of critical-level alerts: 1, > 0, critical Number of warning-level alerts: 1, > 0, warning... Only alert levels with more than 0 alerts are displayed.
   MySQL auto-increment column	MySQL auto-increment column check	Auto-increment column: column 1 in table 1. Tenant: tenant1. Database: db1. Current value of the auto-increment column: 10000, > 2000. Failed
   Partition availability by the time column	Availability check for partitions by the time column	Table: table 1. Tenant: tenant1. Database: db1. Available days of partitions of the current table: < 10 days. Failed
   Sequence availability	Sequence availability check	Sequence: sequence1. Tenant: tenant1. Database: db1. Values assigned to the current sequence: 1000, > 800. Failed

Check the compaction status of a cluster

Check the compaction status of a cluster in OCP

• On the Health Inspection page, view the cluster compaction status.

• The alerting mechanism of OCP monitors the cluster compaction status. When the offset between the freeze version and the baseline version reaches 2, the compaction is considered not completed, and data is frozen again. In this case, an alert is triggered.

You can check the status of a cluster based on the metrics displayed by the Metric parameter. The following table describes the cluster metrics.

Use the relevant view

You can execute the following statement to check the cluster compaction status in the returned results:

obclient> SELECT info FROM __all_zone;

• If the returned result is IDLE for a cluster, the compaction status of the cluster is healthy.

• If the returned result is not IDLE for a cluster, the compaction status of the cluster is abnormal. In this case, troubleshooting is required.