This page displays the overall status of the high-available cluster. In addition, this page provides tools to create, remove, and manage high-availability clusters and the two hosts.
The first section displays the overall status of the high-availability cluster, as well as notifications when errors occur. The table below shows the messages you might see:
Status | Description |
---|---|
Normal | Everything in the cluster working as expected, with data being replicated and the auto-failover function available. |
Processing | The system is processing certain opreations, such as data replication, volume repair/expansion and more. The auto failover function will not be available when the system is in this status. For more details, please refer to Switchover/Auto Failover. |
Upgrading | The system or the package is upgrading. The auto failover function will not be available when the system is in this status. |
Warning | The system has detected errors in the cluster, but the services are still working. The auto failover function may not be available when the system is in this status. All errors must be addressed as soon as possible. |
Critical | The system has detected critical error(s) in the cluster, and the hosts are not able to run the usual services. All errors must be addressed as soon as possible. Under certain cases, usually caused by network abnormality, the system may encouter a split-brain error, and the system would be unable to determine which host runs as the active server. In such cases, all services are suspended to avoid further data inconsistency until the issues are resolved. |
The following table displays some common abnormal status when errors occur in the system. When more than one warning message appear, the most important ones will be displayed and required to be addressed first.
Warning/Error | Description |
---|---|
Monitored service error | An error occurred on one or more monitored services. |
Storage space degraded | A storage space (e.g. RAID Group, Disk Group, volume, iSCSI LUN and SSD cache) on the active or passive server is degraded. Please check the Storage page for more information. |
Storage space crashed | A storage space (e.g. RAID Group, Disk Group, volume, iSCSI LUN and SSD cache) on the active or passive server crashed. Please check the Storage page for more information. |
Failed to detect passive server | This error might occur because the passive server is offline or the active and passive servers cannot connect via the Heartbeat connection. In this case, the auto failover will be unavailable. |
Data cannot be replicated to passive server | This error might occur due to a storage volume or disk failure. In this case, the auto failover will be unavailable. Please check the Storage page for more information. |
No passive server in the cluster | If the passive server is removed from the high-availability cluster, this status will be displayed. In this case, the auto failover will be unavailable. If you wish to add the passive server, click the Manage button > Add passive server. When you have added the passive server, a full data replication will be required. |
This part displays the configuration of the cluster in graphics. If there is any error, there will be a warning or a critical icon.
The Heartbeat connection information, such as transfer speed and latency, is also shown here.
There are two buttons below the cluster information section for you to operate on the cluster with:
In this grid, you are able to monitor the important resource usage of the two hosts. Theoretically, the resource usages of the hosts are co-related, but the statistics of the active server would usually be higher, as it is responsible for running all services. You can check the following usage information in this part:
The 5 latest logs will be shown here for you catch up with the recent cluster activities at a glance.