ALM-24008 Flume Server Non Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the non-heap memory usage of the Flume service every 60 seconds. This alarm is generated when the non-heap memory usage of the Flume instance exceeds the threshold for 5 consecutive times. This alarm is cleared when the non-heap memory usage is less than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If the non-heap memory overflows, the service may break down and the Flume instance may be unavailable.

Possible Causes

The non-heap memory of the Flume instance is overused or the non-heap memory is inappropriately allocated.

Handling Procedure

Check non-heap memory usage.

1. Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing Flume Non-Heap Memory Usage Exceeds the Threshold, and view the Location information. Check the name of the host for which the alarm is generated.
2. On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Flume. On the page that is displayed, click the Instance tab. On the displayed tab page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Agent and select Flume Non-Heap Memory Resource Percentage. Then, click OK.
3. Check whether the non-heap memory used by Flume reaches the threshold (80% of the maximum non-heap memory by default).
   • If yes, go to 4.
   • If no, go to 6.

4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > Flume > Configuration. On the page that is displayed, click All Configurations and choose Flume > System. Set -XX: MaxPermSize in the GC_OPTS parameter to a larger value based on site requirements and save the configuration.
   

   If this alarm is generated, the non-heap memory size configured for Flume instance cannot meet service requirements. You are advised to change the value of -XX:MaxPermSize to twice the current non-heap memory size or change the value based on site requirements.

5. Restart the affected services or instances and check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 6.

Collect the fault information.

6. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
7. Expand the Service drop-down list, and select Flume for the target cluster.
8. 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.
9. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.