ALM-12209 Too Many Full GCs for OMS Processes
Alarm Description
The system checks the full GC count of OMS processes every 60 seconds. This alarm is generated when the number of full GCs exceeds the threshold.
The statistical method is Full GC count = Full GC count in the next period – Full GC count in the previous period. By default, an alarm is reported when the Full GC count exceeds 1 for three consecutive checks. You can adjust this threshold via O&M > Alarm > Thresholds > OMS > OMSServices > GC.
This alarm is cleared when the full GC count of the OMS processes is less than or equal to the threshold.
This section applies only to MRS 3.6.0-LTS or later.
Alarm Attributes
| Alarm ID | Alarm Severity | Auto Cleared |
|---|---|---|
| 12209 | Major | Yes |
Alarm Parameters
| Type | Parameter | Description |
|---|---|---|
| Location Information | Source | Specifies the cluster for which the alarm was generated. |
| ServiceName | Specifies the service for which the alarm was generated. | |
| RoleName | Specifies the role for which the alarm was generated. | |
| HostName | Specifies the host for which the alarm was generated. | |
| ProcessName | Specifies the name of the process for which the alarm was generated. | |
| Additional Information | Trigger condition | Specifies the threshold for triggering the alarm. |
Impact on the System
The read and write operations of OMS processes are affected, which may lead to slowed task execution, unexpected service restarts, and false reporting of other alarms.
Possible Causes
The memory of main OMS processes is too high or inappropriately allocated, causing frequent occurrence of the full GC.
Handling Procedure
Check the Full GC count of the OMS process.
- On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, expand the alarm details, record the process name in Location, click the reported host name, and record the service IP address of the host.
- Choose System > OMS, view the Full GCs of an OMS Process - Process Name chart, and check whether the GC count is more than 1 (default value).
- Contact O&M engineers to modify the memory usage configuration of the processes and restart it.
- Check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to Step 5.
Collect fault information.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Expand the Service drop-down list, and select OmmServer for the target cluster.
- Click the edit icon 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.
- Contact O&M engineers and provide the collected logs.
Alarm Clearance
This alarm is automatically cleared after the fault is rectified.
Related Information
None
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot