You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Martin Alderson (JIRA)" <ji...@apache.org> on 2007/04/04 19:09:33 UTC

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

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

Martin Alderson commented on DIRSERVER-894:
-------------------------------------------

Looks like I was mistaken.  The change has to be within a single object (entry) for the problem to occur.

> 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
>
> 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.