index rebuild

[lod <la...@gmail.com>]

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?


-- 
Laura

Storm - FG40K, MBDCh-G, TFP, SM, JM,  AAD, AJ, AS, AG, AR, SJ, SS, SR, SG,
NA, NAJ, NAC, TN-N, NJC, CL3, CL4-H, CL4-F, CGC, TDI
Rogue - ONYX, MBDCH-S, TFP, AD, AG, SJ, SR, NAJ, CL3-F, CL2  (
http://www.powertripp.org/rogue.cfm)
Karma - FM, MBDX, TFE-I, APJ, APR, APK, AD, SR, SS, CL1
Longshot - noisy little puppy, dock-diving phenom, cuddler extraordinare

at the bridge:
Banshee - FM, MBDCh-S, TF-II, NAP, NJP, RN, CGC, TDI
Gambit - FMX, MBM, TFE, NJP, CGC, TDI

Re: index rebuild

[Davide Giannella <da...@apache.org>]

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