[
https://issues.apache.org/jira/browse/JSPWIKI-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975443#action_12975443
]
Janne Jalkanen commented on JSPWIKI-680:
----------------------------------------
Removing the JSPWiki work directory (NOT Tomcat work directory) and restart of
the servlet container *will* force a Lucene rebuild, since the Lucene indexes
are kept in there. It'll just take a while. You should see a message
"rebuilding Lucene index" at startup if you did everything right.
> jspwiki v2.6.2 - no reliable, easy way to rebuild lucene index after a server
> failure
> -------------------------------------------------------------------------------------
>
> Key: JSPWIKI-680
> URL: https://issues.apache.org/jira/browse/JSPWIKI-680
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.6.2
> Environment: linux rhel 3.x and windows xp
> Reporter: jmason
> Priority: Critical
>
> jspwiki v2.6.2 - no reliable, easy way to rebuild lucene index after a server
> failure.
> after a server crash, lucene index may be corrupted. there is no reliable,
> easy way to cleanly rebuild the index from scratch rendering the jspwiki web
> apps useless.
> directions on clearing out the "work" directory where lucene stores info does
> not work. there isn't any doc on the web site to do this reliably. As a
> result a very good product is rendered useless.
> need BETTER logging to show WHICH file fails on lucene.
> need a simple FIX IT to rebuild lucene index from scratch ( like SharePoint
> has )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
