jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From majohnst <m...@lattaoutdoors.com>
Subject Re: Clustering and Index update
Date Fri, 05 Dec 2008 19:27:43 GMT

I've done some more testing and I am stumped. I started node1 on tomcat at
port 8080. I started node2 on another tomcat instance at port 8180. I add
content to node1 and the debug log shows the content was correctly saved.
But nothing ever happens in the node2 logs. When is node2 suppose to notice
the changes? I've seen some people use a syncDelay attribute in their
cluster configuration. What does that do?

majohnst wrote:
> I have jackrabbit setup with a cluster of 2 nodes. Both nodes are running
> on my local computer but through different tomcat webapps. The clustering
> seems to be working correctly. My problem is when I try to search through
> the nodes.
> If I add a new jcr node to cluster node1, the node is added correctly and
> I can immediately search and find that node. But if I try to do the same
> node on cluster node2, I get no results. If I browse the contents of
> node2, I see my new node exists on the cluster. So somehow node2 is not
> indexing the new changes.
> Ex.
> - create new node, my:node and add to cluster node1
> - search for //element(*,my:node) on node1 and I get the new node
> - search for //element(*,my:node) on node2 and I get no results

View this message in context: http://www.nabble.com/Clustering-and-Index-update-tp20794419p20860885.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message