Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Use of the same ElasticSearch infrastructure for several Liferay DXP versions

Written By

Daniel Couso

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • I would like to use the same ElasticSearch installation for different versions of Liferay DXP such as 7.3, 7.4, and 2024.Q3.

Environment

  • Quarterly Releases: 2024.Q3, 2024.Q2, 2024.Q1, 2023.Q4, 2023.Q3
  • Liferay DXP 7.3, 7.4

Resolution

  • It is technically possible to use the same Elasticsearch infrastructure for several different versions of Liferay DXP if the compatibility matrix allows it. However, this is not recommended in production environments for various reasons:

    • Index structure changes between Liferay versions can lead to indexing and search issues.

    • Resource contention: Both Liferay instances will be competing for resources on the same Elasticsearch cluster, potentially impacting performance.

    • Maintenance complexity: Upgrading or maintaining one Liferay version could impact the other if it requires changes to the Elasticsearch cluster.

  • It is generally recommended to have separate Elasticsearch clusters for different Liferay versions, especially in production environments:

    • This ensures optimal performance, stability, and maintainability.

    • Reindexing one of the installations will only affect its own indices within the Elasticsearch cluster.

    • It will prevent the accidental deletion of indices belonging to other installations.

 

 

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