jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@gmx.net>
Subject Re: Removing Index
Date Mon, 04 Jun 2007 09:05:32 GMT
Hi Noah,

Noah Vihinen wrote:
> We've been running into issues with our jackrabbit index on forced 
> shutdowns.  On restarts, we end up getting errors like the following:
> 
> Error indexing root node:
> 
> java.io.IOException: Error indexing root node: 
> b5d9c4a1-07d5-471e-9fc9-e9a2fbd6ae48
>         at 
> org.apache.jackrabbit.core.query.lucene.MultiIndex.<init>(MultiIndex.java:313)

> 
>         at 
> org.apache.jackrabbit.core.query.lucene.SearchIndex.doInit(SearchIndex.java:295) 
> 
>         at 
> org.apache.jackrabbit.core.query.AbstractQueryHandler.init(AbstractQueryHandler.java:44)

[...]
> We attempted to get around this issue by simply deleted the index of the 
> repository (on the particular machine in a cluster) and restarted with 
> no luck.  In the end, the only thing that seems to work is to copy the 
> index directory from one of the other functional machines in our 
> cluster, followed by a restart.
> 
> This seems like a really ugly way of getting around this issue.  Is 
> there something obvious we're doing wrong.  Shouldn't it be possible to 
> add a machine to a cluster with no pre-existing index?  What are we 
> missing?

My guess is, that this happens because content is changed while the new cluster 
node indexes (traverses) the workspace.

Might be related to: http://issues.apache.org/jira/browse/JCR-931

regards
  marcel

Mime
View raw message