Suppose an event is acknowledged on a child node. This acknowledge has a historical ID, meaning it does not have a source node identifier - only the destination node number. Events for child nodes can also be acknowledged on master nodes. Thus, a conflict is possible between an ID generated on the child node and ID generated on the master node.

Four tables are subject to this problem: "events", "acknowledges", "auditlog", "auditlog_details".

Aleksandrs Saveljevs
added a comment - 2011 Oct 14 17:14 The fix does not work.
Suppose an event is acknowledged on a child node. This acknowledge has a historical ID, meaning it does not have a source node identifier - only the destination node number. Events for child nodes can also be acknowledged on master nodes. Thus, a conflict is possible between an ID generated on the child node and ID generated on the master node.
Four tables are subject to this problem: "events", "acknowledges", "auditlog", "auditlog_details".