This section applies only to MRS 3.3.0 or later.
The system checks the direct memory usage of the PolicySync service every 60 seconds. This alarm is generated when the direct memory usage of the PolicySync instance exceeds the threshold (90% of the maximum memory) for five consecutive times. This alarm is cleared when the PolicySync direct memory usage is less than or equal to the threshold.
Alarm ID |
Alarm Severity |
Auto Cleared |
---|---|---|
45290 |
Major |
Yes |
Parameter |
Description |
---|---|
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. |
Direct memory overflow may cause service breakdown.
The direct memory of the PolicySync process is overused or the direct memory is inappropriately allocated.
Check the direct memory usage.
If this alarm is generated, the direct memory configured for PolicySync cannot meet the direct memory required by the PolicySync process. You are advised to check the direct memory usage of PolicySync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by PolicySync. You can change the value based on the actual service scenario. Refer to 2 to view the TokenServer direct memory usage.
When the service is rebooted, it becomes unavailable and can disrupt business operations. When the instance is rebooted, it cannot be used and any tasks running on the current instance node will fail.
Collect fault information.
This alarm is automatically cleared after the fault is rectified.
None.