I meant to add that if I delete the index directory of node2 and then restart tomcat, the index is rebuilt and I can search for my:node correctly in node2. So this is probably an issue of node1 alerting node2 of changes.
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-tp20794419p20794421.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
