Repository Cache in clustered environment

[lorddgab]

Hi,

We have the following system: Two alfresco community 5 instance with a single repository and a  loadbalancer on the top of them.

There is a problem where if i update a document's metadata through InstanceNode1 and I try to open the same document through InstanceNode2, then what i get is not the updated document.

I suspect that the root of this problem is that the updated data is still in the cache of InstanceNode1(it hasn't been writen to the repository yet) when I try to access it through InstanceNode2.

My question is: How can i configure my system so that both of the instance use a single unified cache?

Thank you!

[cesarista · Accepted solution]

Hi:

I think Alfresco Comunity does not include clustering code since Alfresco 4.2.a :

What’s going on with Alfresco clustering? | ECM Architect

Regards.

--C.

[afaust]

Cesar Capillas is correct. The official clustering component which is also the basis for invalidation of stale / obsolete cache entries is only available in Alfresco Enterprise Edition. Even before the complete removal in Alfresco 4.2 the clustering feature was officially not supported for Community Edition and took some work to activate properly.

I am not aware of any existing, open source addon that provides this capability for Community Edition. Myself I have recently started to work on this particular capability as a small commercial addon. You can send me a PM if you would like to know more about this (I have not yet published anything official about it).