Re: Possible transaction issue with LMDB

On Fri, 2018-08-17 at 01:34 +0300, Леонид Юрьев wrote: > Hi, > > Shortly, no issue. > > LMDB provides MVCC via COW, therefore any read transaction see the > constant snapshot of DB, which is correspond to last committed write > transaction at the time when reading was started. > > Any further

Re: Possible transaction issue with LMDB

William Brown wrote: Hi there, While doing some integration testing of LMDB I noticed that there may be an issue with out of order transaction handling. May be? Do you have sample code that demonstrates the existence of the issue? The scenario is: Open Read TXN A Open Write TXN X, and

Re: [LMDB] What pointer is returned with combination of MDB_WRITEMAP and MDB_RESERVE?

> > By accident. Note that LMDB 1.0 supports page checksums, and what you're > doing here > will break those checksums. Will the checksums be mandatory or optional? For InMemory/NoSync case they could add overhead and you already have many options to choose safety vs performance (WRITEMAP,

Possible transaction issue with LMDB

Hi there, While doing some integration testing of LMDB I noticed that there may be an issue with out of order transaction handling. The scenario is: Open Read TXN A Open Write TXN X, and change values of the DB Commit X Open Read TXN B Open Write TXN Y, and change values of the DB Commit Y Open

Re: [LMDB] What pointer is returned with combination of MDB_WRITEMAP and MDB_RESERVE?

Hello, Working with overflow pages directly via pointers outside write transactions works great and it helps that they do not move "by design" in current versions as discussed in this thread. I have two related scenarios that will give a substantial performance boost in my case. *The first

Re: [LMDB] What pointer is returned with combination of MDB_WRITEMAP and MDB_RESERVE?

Victor Baybekov wrote: Hello, Working with overflow pages directly via pointers outside write transactions works great and it helps that they do not move "by design" in current versions as discussed in this thread. I have two related scenarios that will give a substantial performance boost

Re: OpenLDAP instances crashes

On Thu, Aug 16, 2018 at 05:34:55PM +0200, Michael Ströder wrote: On 8/16/18 5:07 PM, Saurabh Lahoti wrote: This overlay was developed in 2006 when our organization moved to OpenLDAP. We just migrated existing config. & data from 2.4.xx (bdb) to 2.4.46 (lmdb). Did you recompile the overlay for

Re: OpenLDAP instances crashes

On 8/16/18 5:07 PM, Saurabh Lahoti wrote: > This overlay was developed in 2006 when our organization moved to > OpenLDAP. We just migrated existing config. & data from 2.4.xx (bdb) to > 2.4.46 (lmdb). Did you recompile the overlay for 2.4.46? I'm also pretty sure that the API changed within the

Re: OpenLDAP instances crashes

Dear, This overlay was developed in 2006 when our organization moved to OpenLDAP. We just migrated existing config. & data from 2.4.xx (bdb) to 2.4.46 (lmdb). *Thanks & Kind Regards,* Saurabh LAHOTI. *Ideas enlighten Innovation**!!!* Please consider the environment before printing this

Re: OpenLDAP instances crashes

On 8/16/18 4:14 PM, Saurabh Lahoti wrote: > Yes, it is. So if slapd is crashing with a custom overlay loaded you should probably ask the author of this overlay what's wrong. Where did you get this overlay from? Ciao, Michael. > > wrote: > > On 8/16/18 2:00

Re: OpenLDAP instances crashes

Yes, it is. *Thanks & Kind Regards,* Saurabh LAHOTI. *Ideas enlighten Innovation**!!!* Please consider the environment before printing this mail..!! On Thu, 16 Aug 2018 at 14:10, Michael Ströder wrote: > On 8/16/18 2:00 PM, Saurabh Lahoti wrote: > > Aug 16 13:21:07 muledeer kernel:

Re: OpenLDAP instances crashes

On 8/16/18 2:00 PM, Saurabh Lahoti wrote: > Aug 16 13:21:07 muledeer kernel: slapd[29253]: segfault at 0 ip > 7fbeddf3af09 sp 7fb72effc480 error 4 in > uniquemember.so.0.0.0[7fbeddf3a000+2000] What is uniquemember.so? Is it a custom overlay? Ciao, Michael. smime.p7s Description:

OpenLDAP instances crashes

Dear, Today, received below error in /var/log/messages with OpenLDAP instance crashing. Aug 16 13:21:07 muledeer kernel: slapd[29253]: segfault at 0 ip 7fbeddf3af09 sp 7fb72effc480 error 4 in uniquemember.so.0.0.0[7fbeddf3a000+2000] Aug 16 13:21:08 muledeer abrt[24629]: Saved core dump