Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-43009 JobHistory2x Process GC Time Exceeds the Threshold
Updated on 2024-09-23 GMT+08:00
View PDF
Share

ALM-43009 JobHistory2x Process GC Time Exceeds the Threshold

Description

The system checks the garbage collection (GC) time of the JobHistory2x Process every 60 seconds. This alarm is generated when the detected GC time exceeds the threshold (exceeds 5 seconds for three consecutive checks.) To change the threshold, choose O&M > Alarm > Thresholds > Spark2x > GC Time > Total GC time in milliseconds (JobHistory2x). This alarm is cleared when the JobHistory2x GC time is shorter than or equal to the threshold.

In MRS 3.3.0-LTS and later versions, the Spark2x component is renamed Spark, and the role names in the component are also changed. For example, JobHistory2x is changed to JobHistory. Refer to the descriptions and operations related to the component name and role names in the document based on your MRS version.

Attribute

Alarm ID

Alarm Severity

Auto Clear

43009

Major

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service name for which the alarm is generated.

RoleName

Specifies the role name for which the alarm is generated.

HostName

Specifies the object (host ID) for which the alarm is generated.

Trigger Condition

Specifies the threshold triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated.

Impact on the System

The process performance deteriorates, and the process can even be unavailable. Historical execution records of Spark tasks cannot be queried.

Possible Causes

The memory of JobHistory2x is overused, the heap memory is inappropriately allocated. As a result, GCs occur frequently.

Procedure

Check the GC time.

  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43009. Check the RoleName in Location and confirm the IP address of HostName.
  2. On the FusionInsight Manager portal, choose Cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > GC Time > Garbage Collection (GC) Time of JobHistory2x from the drop-down list box in the upper right corner and click OK to check whether the GC time is longer than the threshold(default value: 12 seconds).

    • If yes, go to 3.
    • If no, go to 6.
    Figure 1 Garbage Collection (GC) Time of JobHistory2x

  3. On the FusionInsight Manager portal, choose Cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. The default value of SPARK_DAEMON_MEMORY is 4GB. You can change the value according to the following rules: If this alarm is generated occasionally, increase the value by 0.5 times. If the alarm is frequently reported, increase the value by 1 time.
  4. Restart all JobHistory2x instances.

    When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.

  5. After 10 minutes, check whether the alarm is cleared.

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

Collect fault information.

  1. On the FusionInsight Manager interface of active and standby clusters, choose O&M > Log > Download.
  2. Select Spark2x in the required cluster from the Service.
  3. Click 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.
  4. Contact the O&M personnel and send the collected logs.

Alarm Clearing

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

Related Information

None