Hi,
sorry we have found the source of the problem.
The erroneous behaviour was caused by JBoss TreeCache, that we are trying to plug into Jahia. So it was my fault to blame Jahia's search service (clustered environment).
Thank you in any case!
Sergiy
To: <[email protected]>
From: Stéphane Croisier <[EMAIL PROTECTED]>
Date: 2005-10-03 17:22
Subject: Re: Local search indexing in Jahia cluster
Quite strange because Jahia should send some indexation messages when content is entered on node 1 in order to let node 2 also indexed such a content. Are you sure your JMS server is correctly configured? But perhaps there is a bug....
Stéphane
At 14:19 28/09/2005, you wrote:Hello,
I am experiencing a problem with the search index in the cluster environment.
I have two nodes in a cluster. Each of them is configured to use local indexing.
I create some content on one of the nodes, say node1, and it is properly replicated to node2.
But the search index is only properly updated on the node1, but not on the second one.
I will try to set up another scenario, where the indexing is performed only on one node and the index folder is shared among two instances.
I would like to know, if anyone has any experience with Jahia clustering, which scenarios were used for search indexing and were there any problems?
Thanks to all in advance!
Sergiy.
