Skip to main content

Legacy Local Lucene Index File Troubleshooting

The legacy MM search capabilities are implemented by a Lucene search engine with indexes located in in $MM_HOME/data/search
If this Lucene search index directory has been lost, the MM server will automatically recreate it.

If the Lucene search index has been corrupted for any reason (e.g power outage during indexing, out of memory, concurrent write to the index, etc.), then the search index directory can be deleted, and the MM server will automatically recreate it.
Although not officially supported, the Administrator can attempt to use the Lucene CheckIndex to exorcise corrupted documents from the index.
Here are the steps you can follow (replace lucene-xxxxxxxx with the actual directory name of your search index).

cp -R $MM_HOME/data/search/lucene_xxxxxxxx /backup

cd /tmp

mkdir CheckIndex

cd CheckIndex

$MM_HOME/jre/bin/jar -xvf $MM_HOME/tomcat/webapps/MM.war


java -classpath "lib/*" -ea:org.apache.lucene... org.apache.lucene.index

CheckIndex $MM_HOME/data/search/lucene_xxxxxxxx

Examine the output of the above command to see if there is any corrupted segment. If there is run the same command above with an extra option "-exorcise".

You may delete the CheckIndex directory after you are done.

For more details, see more about about Lucene CheckIndex .

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!