Replication problem - Auto node generation on client boot

[johnwalsh]

Greetings,

I've got replication working between two systems. When the slave system starts up, it creates new entries in the alf_node table as well as a new bin file in the data/live/contentstore/date directory. That slave-created entry in the alf_node table causes MySQL errors when the next node is created in the master, because that master replicated node uses an ID already used in the slave (for the automatically created node), so replication fails.

Why is a node automatically created at boot time? Hopefully there's a simple configuration that I can correct to prevent that.

I have auditing turned on on the master. I already found that same type of collision problem if I have auditing turned on on the slave, so I have disabled auditing on the slave.

Thanks,
John

[johnwalsh]

Immediate problem resolved:

http://issues.alfresco.com/browse/AR-2017 details the bug involving workflow happening even in a read-only system. I've made the same modification to WorkflowInterpreter.onBootstrap() that exists in the HEAD to only do the operation if read-only is set to false, and also to comment out the line "interpretCommand("var bpmackage package 1");"

Those changes have stopped the automatic creation of nodes on system startup.


A larger problem with Alfresco replication remains and is detailed here: http://forums.alfresco.com/viewtopic.php?t=11262

John