------=_Part_90349_22260400.1232120449784 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hello, but the problem persist if you do not use sessionlog (that is my case), if you do more then 1000 deletes, the problem will happen too. SessionLog is a in-memory log, so, if you clean out the memory (with a re-start) the problem will happen. This could be a work-around, but do not solve the problem. Best regards, Joao Alfredo. On Fri, Jan 16, 2009 at 1:11 PM, Andreas Schoe <[email protected]> wrote: > Hello, > > at the documentation center. In section the "N-Way Multi-Master > replication" there is a hint that you have to configure > syncprov-sessionlog <size>. > This option is used by file based configuration. > > In dynamic configuration 'olcSessionlog' is described as follows: > ( OLcfgOvAt:1.2 NAME 'olcSpSessionlog' DESC 'Session log size in ops' > SYNTAX OMsInteger SINGLE-VALUE ) > > Best regards > Andreas > > > Adrien Futschik schrieb: > > Thanks a lot ! > > > > This seems to be working fine. Is this documented anywhere ? > > I never saw that option before. > > > > Adrien Futschik > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > Hello, > > > > add olcSpSessionlog to syncprov. I choose 1000 as value. > > > > Best regards > > Andreas > > > -- > > Andreas Schoe > > Abteilung: Daten- und Rechenzentrum (DRZ) > Tel.: +49 (0)331/288-1719 > Fax: +49 (0)331/288-1701 > Email: [email protected] > ___________________________________ > > Helmholtz-Zentrum Potsdam > Deutsches GeoForschungsZentrum - GFZ > Stiftung des =F6ff. Rechts Land Brandenburg > Telegrafenberg, D-14473 Potsdam > > ------=_Part_90349_22260400.1232120449784 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello,<br><br>but the problem persist if you do not use sessionlog (that is= my case), if you do more then 1000 deletes, the problem will happen too.<b= r><br>SessionLog is a in-memory log, so, if you clean out the memory (with = a re-start) the problem will happen.<br> <br>This could be a work-around, but do not solve the problem.<br><br>Best = regards,<br><br>Joao Alfredo.<br><br><br><div class=3D"gmail_quote">On Fri,= Jan 16, 2009 at 1:11 PM, Andreas Schoe <span dir=3D"ltr"><<a href=3D"ma= ilto:[email protected]">[email protected]</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, = 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br> <br> at the documentation center. In section the "N-Way Multi-Master<br> replication" there is a hint that you have to configure<br> syncprov-sessionlog <size>.<br> This option is used by file based configuration.<br> <br> In dynamic configuration 'olcSessionlog' is described as follows:<b= r> ( OLcfgOvAt:1.2 NAME 'olcSpSessionlog' DESC 'Session log size i= n ops'<br> SYNTAX OMsInteger SINGLE-VALUE )<br> <br> Best regards<br> Andreas<br> <br> <br> Adrien Futschik schrieb:<br> <div><div></div><div class=3D"Wj3C7c">> Thanks a lot !<br> ><br> > This seems to be working fine. Is this documented anywhere ?<br> > I never saw that option before.<br> ><br> > Adrien Futschik<br> ><br> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> ><br> > Hello,<br> ><br> > add olcSpSessionlog to syncprov. I choose 1000 as value.<br> ><br> > Best regards<br> > Andreas<br> ><br> </div></div>--<br> <br> Andreas Schoe<br> <br> Abteilung: Daten- und Rechenzentrum (DRZ)<br> Tel.: +49 (0)331/288-1719<br> Fax: +49 (0)331/288-1701<br> Email: <a href=3D"mailto:[email protected]">[email protected]</a><br> ___________________________________<br> <br> Helmholtz-Zentrum Potsdam<br> Deutsches GeoForschungsZentrum - GFZ<br> Stiftung des =F6ff. Rechts Land Brandenburg<br> Telegrafenberg, D-14473 Potsdam<br> <br> </blockquote></div><br> ------=_Part_90349_22260400.1232120449784--
