ALM-50602 CPU Usage of LDMS Compute Instance Exceeded the Threshold
This section applies only to MRS 3.6.0 or later.
Alarm Description
The system checks the average CPU usage of LDMS compute instances every 30 seconds. This alarm is generated when the average CPU usage of the instances is greater than 90%.
This alarm is cleared when the CPU usage of the LDMS compute instances is no more than 90%.
Alarm Attributes
| Alarm ID | Alarm Severity | Auto Cleared |
|---|---|---|
| 50602 | Major | Yes |
Alarm Parameters
| Type | Parameter | Description |
|---|---|---|
| Location Information | Source | Specifies the cluster for which the alarm was generated. |
| ServiceName | Specifies the service for which the alarm was generated. | |
| RoleName | Specifies the role for which the alarm was generated. | |
| HostName | Specifies the host for which the alarm was generated. | |
| Additional Information | Cpu Usage Exceeds The Threshold | Specifies the tenant name of the compute instance for which the alarm was generated and how much the threshold is exceeded. |
Impact on the System
The performance of the LDMS compute instances deteriorates and the service response becomes slow.
Possible Causes
Too many requests are sent to the LDMS frontend.
Handling Procedure
Check whether compute instance resources are properly configured.
- Log in to FusionInsight Manager as an administrator who can access the LDMS web UI.
- Check whether there are too many requests for accessing the LDMS service.
- Check the LDMS service instances with high CPU usage.
- Wait 2 minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to Step 5.
Collect fault information.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Expand the Service drop-down list, select LDMS for the target cluster, and click OK.
- Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
- Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M technical support and send the collected logs.
Alarm Clearance
This alarm is automatically cleared after the fault is rectified.
Related Information
None
What is your overall rating for this page?
Thank 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