[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Sync replication failure during startup.
- To: "William R. Somsky" <somsky@phys.washington.edu>
- Subject: Re: Sync replication failure during startup.
- From: Stelios Grigoriadis <stelios.xx.grigoriadis@ericsson.com>
- Date: Mon, 01 Oct 2007 13:43:31 +0200
- Cc: openldap-bugs@openldap.org
- In-reply-to: <20070928204415.GA7651@annwn.phys.washington.edu>
- References: <1190879783.5150.15.camel@ebcl206.hf.sw.ericsson.se> <1190985618.5150.52.camel@ebcl206.hf.sw.ericsson.se> <20070928204415.GA7651@annwn.phys.washington.edu>
On Fri, 2007-09-28 at 13:44 -0700, William R. Somsky wrote:
> I've had a similar problem here. I don't really have much to
> add in the way of info for tracking it down, but here is an
> additional question:
>
> Once a replica server gets out of sync w/ the master in this way,
> how does one get the replica back in sync? I've not been able
> to figure that out, short of deleting the entire database on
> the replica and rebuilding it from scratch, which can take a
> very long time.
To my knowledge, you can't. Since the replica contextCSN is
timestamped at a later time than the out-of-sync entries,
they can't be synced.
/Stelios