I would have thought for performance it would be a good idea to keep the indexes local to the nodes anyway, so this is perhaps a good thing (short of using a distributed cache/remote expiry notification mechanism).
Looking good for 1.2 ! On 1/27/07, Dominique Pfister <[EMAIL PROTECTED]> wrote:
Currently not. Another nodes in the cluster will be informed about the changes made and individually update their search index. Kind regards Dominique On 1/26/07, Skripnikov <[EMAIL PROTECTED]> wrote: > > Will this clustering support include lucene's index clustering? > > > Dominique Pfister wrote: > > > > Hi Angelo, > > > > On 1/16/07, Angelo Immediata <[EMAIL PROTECTED]> wrote: > >> We are thinking to use jackrabbit for our CMS; we need a cluster feature; > >> it seems > >> that jsckrabbit can't be used in a clustered environment....how can we > >> solve this? > > > > In the soon to be released Apache Jackrabbit 1.2 clustering support > > has been added. Required are a PersistenceManager that uses a shared > > resource (such as a standalone database) and a shared folder needed to > > log changes and synchronize writes. > > > > For more information, please take a look at the following article: > > > > http://comments.gmane.org/gmane.comp.apache.jackrabbit.devel/9381 > > > > Kind regards > > Dominique > > > > > > -- > View this message in context: http://www.nabble.com/JAckrabbit-cluster-tf3021331.html#a8651655 > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
