Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-45179 Number of Failed OBS readFully API Calls Exceeds the Threshold
Updated on 2024-09-23 GMT+08:00
View PDF
Share

ALM-45179 Number of Failed OBS readFully API Calls Exceeds the Threshold

Alarm Description

The system checks whether the number of failed OBS readFully 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 readFully API calls is less than the threshold.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

45179

Minor

Yes

Alarm Parameters

Parameter

Description

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.

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.

Handling Procedure

  1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of failed calls to the OBS readFully interface. In the right pane, set Threshold or Trigger Count to a larger value as required.
  2. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 3.

  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.

  1. On FusionInsight Manager, choose Cluster > Services > meta. On the page that is displayed, click the Chart tab. On this tab page, select OBS data read operation in the Chart Category area. In the Number of failed calls to the OBS readFully interface-All Instances chart, view the host name of the instance that has the maximum number of failed OBS readFully API calls. For example, the host name is node-ana-corevpeO003.

  2. Choose O&M > Log > Download and select meta and meta under it for Service.
  3. Select the host obtained in 4 for Hosts.
  4. 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.
  5. Contact O&M personnel and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None