The system checks the GC duration of the RangerAdmin process every 60 seconds. This alarm is generated when the GC duration of the RangerAdmin process exceeds the threshold (12 seconds by default) for five consecutive times. This alarm is cleared when the GC duration is less than the threshold.
Alarm ID |
Alarm Severity |
Auto Clear |
|---|---|---|
45280 |
Major |
Yes |
Name |
Meaning |
|---|---|
Source |
Specifies the cluster for which the alarm is generated. |
ServiceName |
Specifies the service for which the alarm is generated. |
RoleName |
Specifies the role for which the alarm is generated. |
HostName |
Specifies the host for which the alarm is generated. |
Trigger Condition |
Specifies the threshold for triggering the alarm. |
The RangerAdmin responds slowly.
The heap memory of the RangerAdmin instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.
Check the GC duration.
If this alarm is generated, the heap memory configured for RangerAdmin cannot meet the heap memory required by the RangerAdmin process. You are advised to check the heap memory usage of RangerAdmin and change the value of -Xmx in GC_OPTS to the twice of the heap memory used by RangerAdmin. The value can be changed based on the actual service scenario. For details, see 2.
Collect the fault information.
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.This alarm is automatically cleared after the fault is rectified.
None