On 30/07/2014 17:54, lod wrote: > In our use of jackrabbit we have had times occur where our indices have > gotten screwed up, and we have deleted and rebuilt them to fix our issues. > As our content grows, this solution is not really viable as the rebuild > process consumes way too much time. We are looking for solutions to: > a. What is the possible cause of the indices to become corrupt? > b. How can we detect which are corrupt and which are still valid, and how > do we fix just those that have become invalid. > > On looking at the options for SearchIndex in repository.xml and > workspace.xml, I see the options for enableConsistencyCheck, > forceConsistencyCheck, and autoRepair. If these parameters are all > enabled, will this allow us to detect when the indices get bad and repair > them? > If so, how often is this checking occurring? > Does it cause any performance degradation to have these parameters enabled? > If I remember correctly it happens on reboot. The time for start-up will be delayed depending on the index size.
HTH Davide
