The search service exceed 80% of its allocated memory
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- We sometimes see the following warning in the Cloud console:
The search service exceeded 80% of its allocated memory.
Resolution
- The search service often presents high memory consumption, sometimes even using the entire container’s allotted memory, and is not necessarily a bad thing.
- This behavior is only be problematic if there are actual issues within the search service, such as slowness, dropped connections, or 500 Internal Server Error messages.
- It is not necessarily a problem that Elasticsearch consumes high memory since search containers typically only have one relevant process and Elasticsearch is using that memory available. In fact, since releasing memory is a costly operation, it would be counterproductive to release the memory back to the container, since there is no other process in need of it. Typically, the JVM should eventually release that memory with a garbage collection.
Did this article resolve your issue ?