Did you setup the machines as a Jackrabbit cluster as per [1] right from the start ? And do you have a complete Journal right from the first operation in the JCR (or local state snapshots)
The local state of the Lucene index is dependent on every node in the cluster replaying every event from the Journal to ensure that they all contain the same content. The Journal is also used for sharedItem state invalidation which will ensure that stale items do not get into responses. HTH Ian 1 http://wiki.apache.org/jackrabbit/Clustering On 28 Sep 2010, at 12:11, Dennis van der Laan wrote: > Hi all, > > We are using Jackrabbit 1.6.1 in a production environment. It is > clustered across 6 machines, which all store the Lucene indexes on a > local disk. After using this setup for a couple of months, we are seeing > the Lucene indexes differ per machine. Not only the size of the indexes, > but some documents seem to be indexed on one machine, but not on another > machine. So doing a full-text search (xpath with a ' contains' clause) > will have different results depending on the machine the query is run on. > I am a complete Lucene novice, so my question is: is this > non-deterministic behaviour a characteristic of Lucene (and should we > rebuild all indexes on a regular basis to keep them in sync) or is > something going wrong here? > > Thanks for any help! > Beste regards, > Dennis > > -- > Dennis van der Laan, MSc > Centre for Information Technology > University of Groningen >
