ALM-18030 Container's Failure Ratio on NodeManager Exceeds the Threshold
Alarm Description
NodeManager periodically checks the running status of the Container on an instance every 30 seconds. This alarm is triggered when Container's failure ratio exceeds the threshold for more than three consecutive occurrences.
The alarm is cleared when the Container's failure ratio on the NodeManager instance is lower than the threshold.
This section applies to MRS 3.6.0-LTS and later versions.
Alarm Attributes
| Alarm ID | Alarm Severity | Auto Cleared |
|---|---|---|
| 18030 | Critical (default threshold: 90%) Major (default threshold: 80%) | 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 | Trigger Condition | Specifies the alarm triggering condition. |
Impact on the System
The tasks of upper-layer services (such as HBase and Spark) may fail, interrupting the upper-layer services.
Possible Causes
- NodeManager's processing capability has reached the bottleneck.
- The NodeManager instance configuration is improper or its key files may be damaged.
Handling Procedure
Check whether the NodeManager's processing capability reaches a bottleneck.
- Log in to FusionInsight Manager, and choose O&M > Alarm > Alarms. View and record the NodeManager instance name reported in the alarm details.
- In the alarm list, check if the alarm "ALM-18011 NodeManager GC Time Exceeds the Threshold" is reported and if the reported host name matches the one you obtained in Step 1.
- Rectify the fault by following the handling procedure of "ALM-18011 NodeManager GC Time Exceeds the Threshold".
- Wait 5 minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to Step 5.
Check whether the NodeManager configuration is improper.
- On FusionInsight Manager, choose Cluster > Services > Yarn > Instances. Click the name of the NodeManager instance corresponding to the host obtained in Step 1.
- Choose Configurations > All Configurations > System. Check if the system parameters for the NodeManager instance are appropriately set. If not, adjust the settings, save the changes, and choose More > Restart Instance in the upper right corner. After passing password verification, restart the instance.
- Wait 5 minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to Step 8.
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 Yarn for the target cluster, 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 engineers and provide 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