On Wed, 2016-07-06 at 17:38 +0200, Ludwig Krispenz wrote:
> Hi Noriko,
>
> I have test scenario for not correctly handled modrdns during total init:
>
> - have a database with n entries, n large enough tthat total init takes
> long enough to be able to apply an update while it is running
> -
Hi Noriko,
I have test scenario for not correctly handled modrdns during total init:
- have a database with n entries, n large enough tthat total init takes
long enough to be able to apply an update while it is running
- add two entries
-- n+1: cn=child,$SUFFIX
-- n+2: cn=parent,$SUFFIX
both
On Mon, 2016-07-04 at 09:37 +0200, Ludwig Krispenz wrote:
> On 07/04/2016 01:32 AM, William Brown wrote:
> >>> It's not the "post init" operations I'm worried about.
> >>>
> >>> It's that operations that were part of the init to the consumer are
> >>> replayed from the changelog.
> >>>
> >>>
On 07/04/2016 01:32 AM, William Brown wrote:
It's not the "post init" operations I'm worried about.
It's that operations that were part of the init to the consumer are
replayed from the changelog.
Operations that occurred after the init starts, definitely still need to
be replayed, and this
> >>
> > It's not the "post init" operations I'm worried about.
> >
> > It's that operations that were part of the init to the consumer are
> > replayed from the changelog.
> >
> > Operations that occurred after the init starts, definitely still need to
> > be replayed, and this makes sense.
> >
On 07/01/2016 04:08 AM, William Brown wrote:
On Thu, 2016-06-30 at 14:53 -0700, Noriko Hosoi wrote:
On 06/30/2016 12:45 AM, Ludwig Krispenz wrote:
Hi William,
the reason that after a total init the consumer does not have the
latest state of the supplier RUV and is receiving updates based on
On Thu, 2016-06-30 at 14:53 -0700, Noriko Hosoi wrote:
> On 06/30/2016 12:45 AM, Ludwig Krispenz wrote:
> > Hi William,
> >
> > the reason that after a total init the consumer does not have the
> > latest state of the supplier RUV and is receiving updates based on the
> > RUV at start of the
Hi William,
the reason that after a total init the consumer does not have the
latest state of the supplier RUV and is receiving updates based on the
RUV at start of the total init is independent of the modrdn problem.
When a supplier is performing a total init it is still accepting
changes,