----- Original Message -----
From: "William" <william(a)firstyear.id.au>
Sent: Wednesday, 4 March, 2015 5:54:50 AM
Subject: [389-users] Referential Integrity
According to dirsrv docs  referential integrity should only be
enabled on a single server in a MMR scenario.
My topology is:
ROA <-- MA <--> MB --> ROB
Where RO is a readonly, M is a master. Arrows indicate data flow
Updates to the DS are done through MA or MB.
Should the advice of enabling on only a single host still be held true?
from my understanding, the plugin will generate internal operations which will be
replicated to all the other suppliers and consumers keeping the coherency (integrity) of
entries in all the nodes of the topology.
What are the potential issues of enabling this on multiple hosts? In
I haven't tested but perhaps we could eventually generate some replication conflicts.
I imagine the same operations taking place simultaneously (because of same update
interval) in several masters and being replicated.
Also some performance degradation.
future what would need to change in the plugin to support enabling
multiple hosts if not already possible?
Do you mean with same configuration in all of the masters ? I don't think it's
worth because the operations will be replicated.
Let's think of a normal mod operation. It would be useless to do the same modify
operation in all the masters. It will fail in the second one if the operation has already
been replicated. Or it will generate a conflict if done simultaneously.
In the same way, the internal MOD operations issued by the plugin should be done in only
Perhaps someone else in this alias could give more precise answers ?
Thanks and regards,