ALM-43600 GraphBase Service Unavailable
Alarm Description
The system checks the GraphBase service status every 60 seconds. This alarm is generated when LoadBalancer or GraphServer cannot provide services properly.
This alarm is cleared when either the LoadBalancer or GraphServer service is normal and the system considers that GraphBase recovers.
Alarm Attributes
Alarm ID |
Alarm Severity |
Alarm Type |
Service Type |
Auto Cleared |
---|---|---|---|---|
43600 |
Critical |
Error handling |
GraphBase |
Yes |
Alarm Parameters
Type |
Parameter |
Description |
---|---|---|
Location Information |
Source |
Specifies the cluster for which the alarm is generated. |
ServiceName |
Specifies the service for which the alarm is generated. |
|
RoleName |
Specifies the role for which the alarm is generated. |
|
HostName |
Specifies the host for which the alarm is generated. |
Impact on the System
The GraphServer service cannot be used.
Possible Causes
- The LoadBalancer service is not started.
- The GraphServer service is not started.
- The LoadBalancer node is abnormal.
- The GraphServer node is abnormal.
- The service on which GraphBase depends is abnormal.
Handling Procedure
Check whether the node where GraphBase is deployed is normal.
- On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > GraphBase > Instance.
- Check whether the status of LoadBalancer and GraphServer is Good.
- Select the faulty instance, choose More > Restart Instance, and check whether the instance is successfully started.
- Check whether the value of loadbalancer.floatip is correct.
- Reconfigure the parameter value and restart the GraphBase service.
- Wait for one minute and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 7.
Check the status of DBService, Yarn, HBase, Spark, Zookeeper, Elasticsearch and Kafka.
- Log in to FusionInsight Manager and choose Cluster > Name of the desired cluster > Service.
- Check whether the status of DBService, Yarn, HBase, Spark, Zookeeper, Elasticsearch, and Kafka services is Good.
- Click a component whose status is Not started or Startup failed.
- In the Instances tab, select the faulty instance, choose More > Restart Instance, and check whether the instance can be started successfully.
- Wait for one minute and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 12.
Collect fault information.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Service area, select the following nodes of the desired cluster.
- If the fault is caused by GraphBase, select GraphBase.
- If the fault is caused by services on which GraphBase depends, select the faulty services and the GraphBase service. (The corresponding hosts are automatically selected once you select the services.)
- Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M engineers and provide the collected logs.
Alarm Clearance
This alarm is automatically cleared after the fault is rectified.
Related Information
None.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot