directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Updated: (DIRSERVER-1101) New replicas may never receive some recent modifications
Date Thu, 19 Jun 2008 21:27:45 GMT


Alex Karasulu updated DIRSERVER-1101:

Cool thanks for the heads up.  I guess 1.5.4 or there after is best for a settled API. Let
me push this off to 1.5.5 which is on our roadmap here:

I realized the flux was making it hard to keep up so we kind of pushed things off a tiny bit.

> New replicas may never receive some recent modifications
> --------------------------------------------------------
>                 Key: DIRSERVER-1101
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: mitosis
>    Affects Versions: 1.5.1
>            Reporter: Martin Alderson
>            Assignee: Martin Alderson
>             Fix For: 1.5.3
> 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.

View raw message