You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2009/08/15 10:43:15 UTC

[jira] Updated: (DIRSERVER-894) Older concurrent changes are never replicated

     [ https://issues.apache.org/jira/browse/DIRSERVER-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-894:
----------------------------------------

    Fix Version/s:     (was: 1.5.7)
                   2.0.0-RC1

Moved to 2.0.0-RC1, we won't release a 1.5.7

> Older concurrent changes are never replicated
> ---------------------------------------------
>
>                 Key: DIRSERVER-894
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-894
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: mitosis
>    Affects Versions: 1.5.0
>            Reporter: Martin Alderson
>             Fix For: 2.0.0-RC1
>
>
> 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.