[389-devel] Re: Prereview for ticket #48402 , required by ticket #48380 SynRepl does not handle database re-initialization properly

2016-01-14 Thread Ludwig Krispenz
On 01/13/2016 11:59 PM, Noriko Hosoi wrote: On 01/13/2016 02:34 PM, Mark Reynolds wrote: On 01/13/2016 10:01 AM, Ludwig Krispenz wrote: Ticket 48380 requires that sync repl handles database reinitializations properly, to be able to determine if cookies are presented are valid. To achieve

[389-devel] Re: design review: don't call plugins for retro changelog

2016-01-14 Thread William Brown
On Thu, 2016-01-14 at 15:42 +0100, Ludwig Krispenz wrote: > We had many issues with the retro changelog plugin. The main reason > is  > that the retro CL is a separate backend and if there is more than > one  > regular backend it is easy to run into deadlocks, eg a change in > backend  > A

[389-devel] Re: Prereview for ticket #48402 , required by ticket #48380 SynRepl does not handle database re-initialization properly

2016-01-14 Thread William Brown
On Thu, 2016-01-14 at 15:07 +0100, Ludwig Krispenz wrote: > On 01/13/2016 11:51 PM, William Brown wrote: > > On Wed, 2016-01-13 at 17:34 -0500, Mark Reynolds wrote: > > > On 01/13/2016 10:01 AM, Ludwig Krispenz wrote: > > > > Ticket 48380 requires that sync repl handles database > > > >

[389-devel] Re: design review: don't call plugins for retro changelog

2016-01-14 Thread Mark Reynolds
On 01/14/2016 09:42 AM, Ludwig Krispenz wrote: We had many issues with the retro changelog plugin. The main reason is that the retro CL is a separate backend and if there is more than one regular backend it is easy to run into deadlocks, eg a change in backend A triggers and ADD in theh RCL,

[389-devel] Re: design review: don't call plugins for retro changelog

2016-01-14 Thread Ludwig Krispenz
On 01/14/2016 04:08 PM, Mark Reynolds wrote: On 01/14/2016 09:42 AM, Ludwig Krispenz wrote: We had many issues with the retro changelog plugin. The main reason is that the retro CL is a separate backend and if there is more than one regular backend it is easy to run into deadlocks, eg a