topic Problem with secondary parent associations in cluster in Alfresco Archive

Problem with secondary parent associations in cluster

francescof — Fri, 21 Sep 2007 12:06:31 GMT

Hi,I have a problem with parent associations in my clustered setup (Alfresco 2.1 Community on a JBoss 4.0.5 2-node cluster): newly created nodes and their (primary) parent associations are replicated correctly. Secondary parent assocs are not.HibernateNodeDaoServiceImpl.java look like this in 2.1 Co

Re: Problem with secondary parent associations in cluster

francescof — Tue, 25 Sep 2007 16:30:02 GMT

After deeper investigations I think I have identified the cause of the problem.

I noticed that, after a secondary child assoc creation no transaction is recorded on alf_transaction because newChildAssoc() and deleteChildAssocInternal() in HibernateNodeDaoServiceImpl don't update NodeStatus for the modified node. This way the remote node of the cluster doesn't know anything about the new child association and thus it doesn't update its lucene indexes.

A quick hack that seems to do the job is to add (with a check to execute this code ONLY on non-primary child-assocs) to newChildAssoc() and deleteChildAssocInternal():

NodeStatus nodeStatus = getNodeStatus(nodeRef, true);

nodeStatus.getTransaction().setChangeTxnId(AlfrescoTransactionSupport.getTransactionId());‍‍‍

This way alf_transaction and alf_node_status tables get updated, the remote node updates its lucene indexes and the secondary association is correctly viewable on the remote node web client.

My concern is: is it possible that this change carries dangerous side effects? I'm thinking about possible index corruption. I'm also aware that the hack described is not the best and cleanest solution for the problem. Have you any suggestions for improvements?

Bye.

Re: Problem with secondary parent associations in cluster

derek — Thu, 27 Sep 2007 13:08:13 GMT

Hi,

You are correct on all counts.

The node status updates are all in the NodeService implementation and should really be at that level i.e. nodeDaoService.recordChangeId(nodeRef);. I'll have to play with it a bit to check if there are any further issues. http://issues.alfresco.com/browse/AR-1777

Regards