Check the OBServer node status

This topic describes three ways that you can use to check the OBServer node status.

Check the OBServer node status on the host

1. Log on to the host on which the target OBServer node is located.

2. Run the following command on the command line interface (CLI) to check the observer process.

   ps -ef |grep observer
   root       6136      0 99 11:23 ?        08:53:50 ./bin/observer
   root      20514  19521  0 16:09 pts/25   00:00:00 grep --color=auto observer
   

Check the OBServer node status in the relevant view

obclient> SELECT status FROM oceanbase.__all_server;
+--------+
| status |
+--------+
| active |
| active |
+--------+
2 rows in set (0.00 sec)

• If the returned result for an OBServer node is active, the OBServer node is running properly.

• If the returned result for an OBServer node is inactive, the OBServer node is offline.

• If the returned result for an OBServer node is deleting, the OBServer node is being deleted.

Check the OBServer node status in OCP

Note

The GUI of OceanBase Cloud Platform (OCP) may vary with the version. This topic takes OCP V3.1.1 as an example. For OCP of other versions, see User Guide of the corresponding version.

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 section of the Health Inspection page, view the OBServer node status.

   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 an OBServer node based on the metrics displayed by the Metric parameter. The following table describes the OBServer node metrics.

   Inspection metric	Metric	Sample result
   server_status	operation status: O&M status. status: O&M status.	OBServer: 192.168.1.1. O&M status: stopping, warning
   ob_server_disk_status	disk_in_bytes_used: the size of used disk space in bytes. disk_used_percent: the disk usage.	OBServer: 192.168.1.1. Used disk size: 2 GB. Disk usage: 85%, > 72%, critical /70%, healthy
   ob_server_partition_count	partition_count: the total number of partition replicas.	OBServer: 192.168.1.1. Partition replicas: 30010, > 300x00, critical /20010, healthy