Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

How to properly scale up Search nodes?

Written By

Marcos da Silva Xavier

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

  • How to properly scale up Search nodes instead of deleting the Search service and deploying it again?

Environment

  • Liferay PaaS
  • Liferay DXP 7.4+

Resolution

  • Following the Liferay Cloud Upgrading to a High Availability Subscription documentation, which also describes the procedures to scale up search services, what you need to do is:

    (… to) update the search service to increase its number of instances it uses by increasing the scale property in your project repository’s search/LCP.json file. Increment the value to the next odd number of instances to prevent issues with the service starting (generally from 1 to 3 when upgrading to the High Availability subscription):

    { "kind": "StatefulSet", "id": "search", "image": "liferaycloud/elasticsearch:6.8.13-4.1.1", "memory": 8192, "cpu": 8, "scale": 3, "podManagementPolicy": "Parallel", ... }

    WARNING

    In order to ensure your search service’s instances can connect to each other properly, increase the scale property to an odd number of nodes, and ensure that the podManagementPolicy property is set to Parallel.

    So the advisory in this WARNING must be followed exactly to prevent connection issues.

 

 

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?