ALM-45182 Number of Throttled OBS Operations Exceeds the Threshold
Alarm Description
The system checks whether the number of throttled OBS operations exceeds the threshold every 30 seconds. This alarm is generated when the number of throttled OBS operations exceeds the threshold.
This alarm is automatically cleared when the number of throttled OBS operations is less than the threshold.
Alarm Attributes
Alarm ID |
Alarm Severity |
Auto Cleared |
---|---|---|
45182 |
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
The frequency of requesting OBS APIs is too high.
Handling Procedure
- Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds. On the Thresholds page, choose meta > Number of Throttled OBS Operations. 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 Throttled in the Chart Category area. In the Number of Throttled OBS Operations-All Instances chart, view the host name of the instance that has the maximum number of throttled OBS API calls. For example, the host name is node-ana-coreUQqJ0002.
- 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 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.