[
https://issues.apache.org/jira/browse/DIRSERVER-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542800
]
Martin Alderson commented on DIRSERVER-1101:
--------------------------------------------
I think a simple solution for this will be to just make the final update CSN
vector in the new replica (after it has received all the entries) be that of
the original replica when it started sending the entries. This will mean a lot
of modifications will be sent that have already been applied but they will be
safely ignored by the new replica.
> New replicas may never receive some recent modifications
> --------------------------------------------------------
>
> Key: DIRSERVER-1101
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1101
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: 1.5.1
> Reporter: Martin Alderson
>
> When a new replica is sent all entries from another replica some of the
> earlier entries may not be up to date. If, for example, we send the first
> entry to the new replica then the first entry followed by the last entry are
> modified in turn at the original replica the new replica will never get the
> modification to the first entry.
> This occurs as the new replica will only ever ask for newer logs than it's
> current update CSN vector which will be based on the most recently modified
> entries that it was sent.
> I think that before the new replica is allowed to receive any newer logs we
> will need to go back over each entry that was sent and request the
> modifications to bring each up to the version it should be at. Throughout
> this time all local modifications should be rejected as in DIRSERVER-1098.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
