directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject Re: Replication heads up
Date Mon, 08 Aug 2011 19:10:42 GMT
On 8/8/11 11:35 AM, Kiran Ayyagari wrote:
> On Mon, Aug 8, 2011 at 2:26 PM, Emmanuel Lecharny<>  wrote:
>> Hi guys,
>> One option would be to ask the consumer to send a periodic message to the
>> producer informing it that it's up to date. It could be a daily unbind/bind
>> for instance. The unbind will kill the pending persistent search we
>> established between the producer and consumer, to establish a new one. As we
>> will send a new request, with the lastEntryCSN, we will be able to truncate
>> the provider queue, so it won't grow forever.
> this case is already handled(in my recent commit), i.e., when a
> consumer reconnects we remove all the entries from log that are older
> than the CSN value present in the cookie.
> Coming to restarting the consumer at periodic intervals is an
> interesting idea, this perfectly solves many cases of 'how to
> prune/truncate the log' except in cases of a consumer that never
> reconnects, in which case we need to go for a time based policy

I ran the tests 100 times in a row, no error. Seems like your fix was 
the correct one.

Emmanuel L├ęcharny

View raw message