On this page

Show all

Help Center/ MapReduce Service/ User Guide (Ankara Region)/ Alarm Reference/ ALM-51202 LakeSearch Heap Memory Usage Exceeds the Threshold

ALM-51202 LakeSearch Heap Memory Usage Exceeds the Threshold

Updated on 2024-11-29 GMT+08:00

View PDF

Alarm Description

The system checks the heap memory usage of LakeSearch every 60 seconds. This alarm is generated when the number of times that the heap memory usage exceeds the threshold reaches the alarm trigger count.

If Trigger Count is 1, this alarm is cleared when LakeSearch heap memory usage is less than or equal to the threshold. If Trigger Count is greater than 1, this alarm is cleared when LakeSearch heap memory usage is less than or equal to 90% of the threshold.

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
51202	Critical (default threshold: 95%) Major (default threshold: 90%)	Quality of service	LakeSearch	Yes

Alarm ID

Alarm Severity

Alarm Type

Service Type

Auto Cleared

51202

Critical (default threshold: 95%)

Major (default threshold: 90%)

Quality of service

LakeSearch

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.
Additional Information	Trigger Condition	Specifies the threshold for triggering the alarm.

Impact on the System

If the available LakeSearch heap memory is insufficient, the LakeSearch semantic search performance is affected, and even memory overflow occurs. As a result, the LakeSearch instance process becomes unavailable.

Possible Causes

LakeSearch heap memory is insufficient.

Handling Procedure

Check the LakeSearch JVM memory configuration and adjust it.

Log in to FusionInsight Manager and choose Cluster > Services > LakeSearch. Click Configurations and click All Configurations.
In the upper right corner of the configuration page, enter GC_OPTS in the search box. The GC_OPTS parameters of all instances are displayed.

Select the instance whose parameter GC_OPTS needs to be modified, and check whether the differentiated configuration icon is displayed next to the instance value configuration box.
- If the icon is displayed, go to 4.
- If the icon is not displayed, go to 5.
Click . In the displayed dialog box, click on the right and click OK.
Change the values of -Xms and -Xmx of the GC_OPTS parameter by referring to the following note.
NOTE:
Suggestions on GC parameter settings for LakeSearch instances:
- Change the values of -Xms and -Xmx of the GC_OPTS parameter to 8G.
- Set -Xms and -Xmx to the same value to prevent dynamic adjustment of the heap memory size, which may affect performance.
After the modification, click Save in the upper left corner. In the displayed dialog box, click OK.
Click Instances, select the instances whose configuration status is Expired, and choose More > Restart Instance to restart them as prompted.
Wait for one minute and check whether the alarm is cleared.
- If the alarm is cleared, no further action is required.
- If the alarm is not cleared, go to 9.

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 LakeSearch 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 personnel and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None

Parent topic: Alarm Reference

Previous topic: ALM-51201 LakeSearch Unavailable

Next topic: ALM-51203 GC Duration of the LakeSearch Instance Exceeds the Threshold

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

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.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot