ALM-50209 Failures to Generate Doris Metadata Image Files Exceed the Threshold
Alarm Description
The system checks the number of failures to generate metadata image files on the FE node every 30 seconds. This alarm is generated when the number of failures exceeds the threshold (1 by default).
This alarm is cleared when the system detects that the number of failures is less than the threshold.
Alarm Attributes
Alarm ID |
Alarm Severity |
Alarm Type |
Service Category |
Auto Cleared |
---|---|---|---|---|
50209 |
Minor |
Error handling |
Doris |
Yes |
Alarm Parameters
Category |
Parameter |
Description |
---|---|---|
Location Information |
Source |
Specifies the cluster or system 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. |
|
Additional Information |
Detail |
Specifies the alarm triggering condition. |
Impact on the System
The non-master FE node cannot receive the latest metadata image file. As a result, the system reliability deteriorates.
Possible Causes
When the checkpoint thread of the Doris FE detects that the FE heap memory usage exceeds 75% (70% for MRS 3.5.0-LTS or later), the thread determines that the write operation to the image file fails.
Handling Procedure
Check the Doris service status.
- On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, view the role name and obtain the IP address of the instance in Location of the alarm whose ID is 50209.
- Choose Cluster > Services > Doris > Instances, click the FE instance for which the alarm is generated, and click the Chart tab of the instance.
Select CPU and Memory from chart categories on the left, and check whether the value of FE Heap Memory Usage Rate exceeds 75%. The value is 70% for MRS 3.5.0-LTS and later versions.
- Choose Cluster > Service > Doris, and click the Configurations tab. Search for FE_GC_OPTS in the search box, and increase the value of -Xmx. The default value is 8GB.
- If this alarm is occasionally generated, increase the value by 50%. If this alarm is frequently generated, double the value.
- In the case of large service volume and high service concurrency, you are advised to add instances.
- Click Save. Click Instances, select an FE instance whose configuration has expired, and choose More > Restart Instance.
During FE instance restart, the tasks running on FE nodes will fail. The tasks on FE nodes that are not restarted are not affected.
- After restart, check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to Step 6.
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, select Doris for the target cluster, and click OK.
- 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.
- Send the collected fault logs to O&M personnel for help.
Alarm Clearance
You need to manually clear the alarm after the fault is rectified.
Related Information
None.
Feedback
Was this page helpful?
Provide feedbackThank 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