[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Sync replication, with failing consumer
- To: Marc Roos <M.Roos@f1-outsourcing.eu>, openldap-technical <openldap-technical@openldap.org>
- Subject: Re: Sync replication, with failing consumer
- From: Howard Chu <hyc@symas.com>
- Date: Fri, 6 Dec 2019 13:18:20 +0000
- In-reply-to: <"H000007100159474.1575625885.sx.f1-outsourcing.eu*"@MHS>
- References: <"H000007100159474.1575625885.sx.f1-outsourcing.eu*"@MHS>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53
Marc Roos wrote:
>
> With sync replication, having a provider at state C (newest) and a
> consumer starting with rid=100 and state=A.
>
> After syncing provider and consumer both are in state C
>
> When then the consumer is killed, and a new consumer is started with the
> same rid=100 and again state A.
>
> Does this consumer sync data from the provider again?
If the consumer is at state A, then of course it must retrieve data from the
provider again to arrive at state C. The data can't just magically appear on
the consumer out of thin air.
> Or does the
> provider has data stored of the previous consumer and block syncing?
How would it do that? And how would storing special data on the provider help in
any way to bring the new consumer to state C?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/