Support Article
Reindexing failed
Summary
User complained that Re-indexing is failed on clicking the re-index button.
Indexing is fine for rule but the issue is with Data and Work.
Error Messages
No such error message.
Steps to Reproduce
Re-indexing failed when clicking the re-index button.
Root Cause
Occasionally, there is an error if, for some reason, this .lock file is not deleted. (This may occur if, for example, PegaRULES is terminated when Lucene is in the middle of writing to an index, or some other PegaRULES error occurs.) When the system is restored, the indexing operations will fail; the next time indexing is attempted, Lucene tries to take out a lock on the index file, and fails, as there is already an existing "lock" on the file – the .lock file already exists on the disk. Lucene will wait some amount of time for the index to be "free" and the lock to be "released" (deleted), which will never happen, as it was left by mistake, and will eventually time out with the error
Resolution
Deleting the lock file resolved the issue
Remove the .lock file, restart your PRPC server, and rebuild the indexes by following these steps:
1. Stop the Indexing Agents.
2. Delete the write.lock file.
3. Restart the server.
4. Run the Indexing using SMA.
5. Start the Indexing Agents.
If it is a multinode environment and if the Indexing agents are enabled on al the nodes, this causes an issue.
If so then enable indexing agents only on the Indexing node and stop the agents on all the other nodes.
Published May 14, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.