You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@jackrabbit.apache.org by majohnst <ma...@lattaoutdoors.com> on 2008/12/02 17:38:24 UTC

Clustering and Index update

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



<?xml version="1.0" encoding="ISO-8859-1"?>
<Repository>
	<Cluster id="node1">
		<Journal class="org.apache.jackrabbit.core.journal.DatabaseJournal">
			
			
			
			
			
			
		</Journal>
	</Cluster>


	<FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
		
		
		
		
		
		
	</FileSystem>

	<Security appName="Jackrabbit">
		<AccessManager
			class="org.apache.jackrabbit.core.security.SimpleAccessManager" />
		<LoginModule class="org.apache.jackrabbit.core.security.SimpleLoginModule"
/>
	</Security>

	<Workspaces rootPath="${rep.home}/workspaces"
		defaultWorkspace="default" />
	<Workspace name="${wsp.name}">

		<FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
			
			
			
			
			
			
		</FileSystem>
		<PersistenceManager
		
class="org.apache.jackrabbit.core.persistence.bundle.MySqlPersistenceManager">
			
			
			
			
		</PersistenceManager>

	<SearchManager
        class="org.apache.jackrabbit.core.query.xpath.XPathQueryBuilder" /> 
        
		<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
			
		</SearchIndex>

	</Workspace>
	<Versioning rootPath="${rep.home}/versions">
		
		<FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
			
			
			
			
			
			
		</FileSystem>

		<PersistenceManager
		
class="org.apache.jackrabbit.core.persistence.bundle.MySqlPersistenceManager">
			
			
			
			
		</PersistenceManager>
	</Versioning>

 <SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
        
    </SearchIndex>

		
</Repository>

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

Re: Clustering and Index update

Posted by majohnst <ma...@lattaoutdoors.com>.

Ahh, thank you. I started looking at my configurations and I noticed that my
schemaObjectPrefixes were not matching up between the two nodes. Once I got
that all straightened out it worked. Thanks.



Jukka Zitting wrote:
> 
> Hi,
> 
> On Fri, Dec 5, 2008 at 8:27 PM, majohnst <ma...@lattaoutdoors.com> wrote:
>> 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.
> 
> Are your nodes looking at the same journal database?
> 
> BR,
> 
> Jukka Zitting
> 
> 

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

Re: Clustering and Index update

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Fri, Dec 5, 2008 at 8:27 PM, majohnst <ma...@lattaoutdoors.com> wrote:
> 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.

Are your nodes looking at the same journal database?

BR,

Jukka Zitting

Re: Clustering and Index update

Posted by majohnst <ma...@lattaoutdoors.com>.

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.

Re: Clustering and Index update

Posted by majohnst <ma...@lattaoutdoors.com>.

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.