RE: Store lucene index file into database with clustering

[Luis Leong]

Yes, the machine A config as follow
<Cluster id="node_1">
                <Journal
        
class="org.apache.jackrabbit.core.journal.DatabaseJournal">
                        <param name="revision" value="${rep.home}/revision"
/>
                        <param name="driver" value="com.mysql.jdbc.Driver"
/>
                        <param name="url"
        
value="jdbc:mysql://192.168.101.122:3306/repositorytest?useUnicode=true&amp;
characterEncoding=UTF-8&amp;autoReconnect=true" />
                        <param name="user" value="luis" />
                        <param name="password" value="luis" />
                        <param name="schema" value="mysql" />
                        <param name="schemaObjectPrefix" value="J_C_" />
                </Journal>
        </Cluster>

In machine B, simply change node_1 to node_2

-----Original Message-----
From: Matej Knopp [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 02, 2008 5:36 PM
To: users@jackrabbit.apache.org
Subject: Re: Store lucene index file into database with clustering

Do you have the journal properly configured?

-Matej

On Mon, Jun 2, 2008 at 10:50 AM, Luis Leong <[EMAIL PROTECTED]>
wrote:
> Dear developers,
>
>
>
> I have made clustering node_1 and node_2 in machine A and B respectively
> with BundlePersistenceManager on a MySQL DB.
>
>
>
> I executed the an ocm application on both machine A and B. Each node
insert
> different content (say cA and cB) . (It succeed)
>
>
>
> Then I executed another program using query to search back the content (cA
> and cB) I have inserted. But in machine A, only cA can be searched and in
B,
> only cB can be searched)
>
>
>
> I am wondering the problem may be on ocm query manager which uses lucene
> indexer because node_1 and node_2 built their own indices .
>
> Can anyone tell me how to persist the index information in database, or
some
> other method to solve my problem?
>
>
>
> Best Wishes
>
>
>
> Luis
>
>