Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Reindex Required After New Deployment

Written By

Jamilly Macedo

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

  • When performing a new deployment, a complete reindex process is required for the contents to be displayed again.

Environment

  • Liferay PaaS

Resolution

  • Verify if the indexes are stored on a persistent volume. This ensures that the index data remains intact even during deployments or system restarts.

    Example of LCP.json configuration for the Search service:

"volumes": {
    "esdata": "/data"
  },
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?