topic Re: When should NodeStatus (alf_node_status table) be updated? in Alfresco Archive

When should NodeStatus (alf_node_status table) be updated?

francescof — Wed, 26 Sep 2007 16:03:42 GMT

I'm asking the question "when should NodeStatus (alf_node_status table) be updated?" because I ran in the same problem two times in a few days.The first is described here: http://forums.alfresco.com/viewtopic.php?t=8772The second is similar, and has a similar solution…I noticed that, in a two node c

Re: When should NodeStatus (alf_node_status table) be updated?

andy — Thu, 11 Oct 2007 13:40:42 GMT

Hi

The lucene indexes on the two nodes will be tracking the changes made by the other. The changes are not indexed atomically over the cluster. XPath goes against the node service/DB so should be correct if your clustred cache configuration is correct.

You can configure how aggressive the tracking job is at keeping up to date.

Support to share the lucene index is on going. This will remove this issue.

Andy

Re: When should NodeStatus (alf_node_status table) be updated?

francescof — Mon, 15 Oct 2007 10:47:45 GMT

What I noticed is that, on 2.1, XPath goes on Lucene and selectNodes() goes on Jaxen XPath so it really was a matter of indexes not being updated.

I've applied manually the fixes related to JIRA AR-1777 but it seems that the remote node still doesn't update its indexes. Adding a call to getHibernateTemplate().saveOrUpdate(status) in the else block in HibernateNodeDaoServiceImpl.recordChangeId() seems to do the trick.

Bye.