ALM-45181 Number of Failed OBS write API Calls Exceeds the Threshold¶
Description¶
The system checks whether the number of failed OBS write API calls exceeds the threshold every 30 seconds. This alarm is generated when the number of failed API calls exceeds the threshold.
This alarm is automatically cleared when the number of failed OBS write API calls is less than the threshold.
Attribute¶
Alarm ID | Alarm Severity | Auto Clear |
|---|---|---|
45181 | Minor | Yes |
Parameters¶
Name | Meaning |
|---|---|
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. |
Trigger Condition | Specifies the threshold for triggering the alarm. |
Impact on the System¶
Certain upper-layer big data computing tasks will fail to execute.
Possible Causes¶
An execution exception or severe timeout occurs on the OBS server.
Procedure¶
Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS write interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
Check whether the alarm is cleared.
If yes, no further action is required.
If no, go to 3.
Contact OBS O&M personnel to check whether the OBS service is normal.
If yes, go to 4.
If no, contact OBS O&M personnel to restore the OBS service.
Collect fault information.
On FusionInsight Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data write operation in the Chart Category area. In the Number of failed calls to the OBS write interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS write API calls. For example, the host name is node-ana-corevpeO003.
Choose O&M > Log > Download and select meta and meta under it for Service.
Select the host obtained in 4 for Hosts.
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 personnel and provide the collected logs.
Alarm Clearing¶
This alarm is automatically cleared after the fault is rectified.