Cluster Issues - New Content not showing on other servers

[curious_george]

I'm running Alfresco 2.1 CE on Linux. I've created a clustered Alfresco environment on two servers. They share the same content store (and use local lucene index directories, of course). Despite having followed the Wiki instructions to the dot, I am still having issues with clustering. If I create a document on one machine (e.g. ServerA), it does not show up on the other machine, ServerB. Both servers have their times synchronized via ntpd.

I turned up debug logging for the ehcache methods. I can see that the servers are receiving heartbeats from each other every 10 seconds. Furthermore, if I create a document on ServerB, I can see entries on ServerA's log file that display the following:

2008-04-25 09:41:23,681 DEBUG [net.sf.ehcache.distribution.RMICachePeer] Remote remove received for key: org.alfresco.repo.domain.hibernate.NodeImpl#104096
2008-04-25 09:41:23,683 DEBUG [net.sf.ehcache.distribution.RMICachePeer] Remote remove received for key: alf_node_status
2008-04-25 09:41:23,735 DEBUG [net.sf.ehcache.distribution.RMICachePeer] Remote remove received for key: org.alfresco.repo.domain.hibernate.NodeStatusImpl#NodeKey[ id=6d44db9a-12e6-11dd-bd5e-8742755ac402, protocol=workspace, identifier=SpacesStore]
‍‍‍‍

How come documents created on ServerA do not show up on ServerB? If I restart the Alfresco server, the documents will appear (I presume this is due to the lucene indexes being recreated)

Here is the relevant portion of my custom-repository.properties:

index.recovery.mode=AUTO
db.schema.update=false

index.tracking.cronExpression=0/10 * * * * ?
index.tracking.adm.cronExpression=${index.tracking.cronExpression}
index.tracking.avm.cronExpression=${index.tracking.cronExpression}
index.tracking.maxTxnDurationMinutes=60
index.tracking.reindexLagMs=1000
index.tracking.maxRecordSetSize=1000
‍‍‍‍‍‍‍‍‍‍

I have ehcache-custom.xml in my {extRoot}/alfresco/extension directory. Both servers use the same multicast address and ports.  Being that it's a very large file, here's the top portion of it:

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic,
                        multicastGroupAddress=230.0.0.1,
                        multicastGroupPort=4446"/>‍‍‍‍‍

Thanks in advance for any responses - looking through the forums, I see that this is an issue that a few other people have encountered with varying degrees of success.

[curious_george]

FYI, I think I solved it. The instructions on the wiki appear to be a bit misleading. The index tracking parameters should NOT be put in the custom-repository.properties file for Alfresco 2.1 CE. (But according to the Wiki, it needs to be in that file for 1.4.5 and later).

Hope the solution helps.

This issue was a major pain in the rear…

[ds-crcpress]

I too had the same issue.  Your note helped.  The wiki is not wrong, but very confusing because there are two pages with essentially the same information.  The released CE is 2.1.0, and they changed the cluster config via properties in 2.1.3.  :!:

I would have marked this post as helpful, but unfortunately I did not post the question. 

Thanks!

[marchoon]

I have the same problem. but according to your answer, I don't understand where I have to configure index tracking. Is it in the repository.properties file, or in the index-tracking-context.xml file, or an other file? If I do in both of them, it doesn't work. could you help me?

[ds-crcpress]

What version of Alfresco are you running (including minor revision)?

[somervill]

I´m having the same problem as well.where I have to configure index tracking?

I´m using Alfresco CE version 2.1.0 (484)

Thanks

[amitabhandari1]

HI

I am also facing the same issue , can you please suggest what chnages you have made to overcome this.