Legacy Knowledge Base
Published Jul. 2, 2025

Missing Search Indices After Restart/Redeploy

Written By

Justin Bowman

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.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • Upon restarting or redeploying the search service, you may notice that Liferay indices may be missing within your environment. Restarting or Redeploying a service that does not have a volume set can lead to this behavior.

Environment

  • Liferay PaaS

Resolution

  • To avoid having to reindex for future restarts or redeployments, please be sure to set a volume for the search service within the LCP.json file:
"volumes": {
    "esdata": "/data"
  }
  • You will need to perform a reindex in order to rebuild the search indices following a restart or redeploy. As reindex processes may take a long time, please schedule this during your maintenance hours as to not impact users.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base