The system checks the direct memory usage of the TagSync service every 60 seconds. This alarm is generated when the direct memory usage of the TagSync instance exceeds the threshold (80% of the maximum memory) for five consecutive times. This alarm is cleared when the TagSync direct memory usage is less than or equal to the threshold.
Alarm ID |
Alarm Severity |
Auto Clear |
|---|---|---|
45286 |
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. |
Direct memory overflow may cause service breakdown.
The direct memory of the TagSync instance is overused or the direct memory is inappropriately allocated. As a result, the memory usage exceeds the threshold.
Check the direct memory usage.
If this alarm is generated, the direct memory configured for TagSync cannot meet the direct memory required by the TagSync process. You are advised to check the direct memory usage of TagSync and change the value of -XX:MaxDirectMemorySize in GC_OPTS to the twice of the direct memory used by TagSync. You can change the value 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