Legacy Knowledge Base
Published Jul. 2, 2025

Can my installation be recovered from a corrupted Lucene index without performing a full reindexing?

Written By

Daniel Couso

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

  • There is one or more error messages containing information similar to the following lines in one of the cluster nodes log:
    Initializing Lucene writer failed for 155
    java.io.IOException: read past EOF:MMapIndexInput(path="/opt/liferay/data/lucene/155/segments_645o4q")

Environment

  • Liferay Portal 6.2

Resolution

  • Given that the following properties are enabled:
    cluster.link.enabled=true
    ehcache.cluster.link.replication.enabled=true
    lucene.replicate.write=true
  • It would be possible to avoid a full reindexing by forcing to load the master node's indexes into the slave node. These would be the steps:
    1. Make a functional backup of the installation in case it were necessary to go back. 
    2. Stop the affected node (only the affected node) . After it stops the remaining active node should be selected as Lucene Master node automatically.
    3. Delete <LIFERAY_HOME>/data/lucene folder in the affected node.
    4. Start the affected node.
    5. Wait until the indexes can be fully loaded from master node:
      • This reindexing may take some considerable time depending of the volume of the current data.
      • Likewise, while the index is being regenerated, some queries may not be available from that node until the reindexing is completed.
Did this article resolve your issue ?

Legacy Knowledge Base