Help Center/ MapReduce Service/ User Guide (Ankara Region)/ Alarm Reference/ ALM-43611 Number of GC Times of the Old-Generation GraphServer Process Exceeds the Threshold
Updated on 2024-11-29 GMT+08:00

ALM-43611 Number of GC Times of the Old-Generation GraphServer Process Exceeds the Threshold

Alarm Description

The system checks the number of GC times of the old-generation GraphBase service every 30 seconds. This alarm is generated when the number of GC times of the old-generation GraphBase service exceeds the threshold (the number of GC times exceeds 5 seconds for three consecutive times by default). On the FusionInsight Manager homepage, choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > GraphBase > GC Count > Number of GC Times of the Old-Generation GraphServer Process. This alarm is cleared when the number of GC times of the old-generation GraphBase service is less than or equal to the threshold.

If the multi-instance function is enabled in the cluster and multiple HBase services are installed, determine the GraphBase service for which the alarm is generated based on the value of ServiceName in Location Information of the alarm. For example, if the GraphBase1 service is unavailable, the service name displayed in Location Information is GraphBase1 and the operation object in the handling procedure is changed to GraphBase1.

Alarm Attributes

Alarm ID

Alarm Severity

Alarm Type

Service Type

Auto Cleared

43611

Major

Quality of service

GraphBase

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Indicates the service for which the alarm is generated.

RoleName

Indicates the role for which the alarm is generated.

HostName

Indicates the host for which the alarm is generated.

Impact on the System

If the number of GC times of the old-generation GraphServer exceeds the threshold, the GraphBase interface cannot be accessed normally.

Possible Causes

The memory of GraphBase instances on the node is overused, the heap memory is inappropriately allocated, or a large number of I/O operations exist in GraphBase. As a result, GCs occur frequently.

Handling Procedure

Check the number of GC times.

  1. On the FusionInsight Manager homepage, choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > GraphBase > GC Count > Number of GC Times of the Old-Generation GraphServer Process.
  2. On the FusionInsight Manager homepage, choose Cluster > Name of the Desired cluster > Service > GraphBase. Click the drop-down list in the upper right corner of the graph area, choose Customize > Number of GC Times of the Old-Generation GraphServer Process, and click OK to check whether the threshold is exceeded.

    • If yes, go to 3.
    • If no, go to 5.

  3. On the FusionInsight Manager homepage, choose O&M > Alarm > Threshold Configuration > Name of the desired cluster > GraphBase > GC Count > Number of GC Times of the Old-Generation GraphServer Process to reset the threshold.
  4. Wait for one minute and check whether the alarm is cleared.

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

  5. Stop sending any requests for creating, deleting, updating, or querying relationships.

    Wait for one minute and check whether the alarm is cleared.
    • If yes, no further action is required.
    • If no, go to 6.

Collect the fault information.

  1. On the FusionInsight Manager homepage, choose O&M > Log > Download.
  2. Expand the Service drop-down list, and select GraphBase for the target cluster.
  3. 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.
  4. Contact O&M engineers and provide the collected logs.

Alarm Clearance

After the fault is rectified, the system automatically clears this alarm.

Related Information

None.