Yep this is the biggest problem right now with mitosis. I plan to get down and dirty with a redesign of Mitosis right after the 1.5.0 and 1.0.2 releases.
This is the highest priority for 1.5.1 as far as many of us are concerned.
The current replication capabilities are not production ready or recommended for anything other than a feature preview for experimentation.
On 4/3/07, Martin Alderson (JIRA) <firstname.lastname@example.org> wrote:
Older concurrent changes are never replicated
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.0
Reporter: Martin Alderson
When a (non-conflicting) change is made in two replica peer servers (A and B) at once, A's changes are replicated to B, but B's changes are never replicated to A. This leads to inconsistent trees. The two changes made can be totally unrelated (
e.g. setting an attribute in two separate objects).
This is easy to reproduce by having two replica servers set up, disabling the network link, making a separate change on each server,then re-enabling the network link. Only one server will have both changes, the other will only have its own change.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.