MDB_TOOL mode vs. large mdb_env_set_maxreaders()?
by Hallvard Breien Furuseth
If an lmdb application configures a non-default maxreaders,
this setting is ignored if a tool like mdb_copy is already
running (maybe from crontab).
I suggest mdb_copy & co should use an MDB_TOOL env flag
which requires the lockfile (if any) to be valid, and only
partly reinitializes it. The upcoming MDB_ROBUST flag might
also make use of this. An alternative would be to stuff
this into the metapages, but that seems less flexible.
--
Hallvard
8 years, 9 months
RE24 Testing Call #4
by Quanah Gibson-Mount
Should be the final testing call. Please test and report back, thanks!
--Quanah
--
Quanah Gibson-Mount
Server Architect
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
8 years, 9 months
RE24 Testing call #3 (OpenLDAP 2.4.40)
by Quanah Gibson-Mount
Hopefully the final testing call. Please test and report back, thanks!
--Quanah
--
Quanah Gibson-Mount
Server Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
8 years, 9 months
DTLS, cldaps?
by Howard Chu
Was just reviewing the latest OpenSSL security advisories, many of which apply
to their DTLS implementation. I usually ignore anything that has to do with
DTLS since LDAP is connection-oriented and not datagram based, but now it
occurs to me to ask - is anyone using LDAP over UDP with DTLS?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
8 years, 10 months
Re: openldap.git branch mdb.master updated. 3630066843b7ca6b2cd12911d3e2fe3314cd4549
by Hallvard Breien Furuseth
On 27/07/14 03:27, openldap-commit2devel(a)OpenLDAP.org wrote:
> commit 3630066843b7ca6b2cd12911d3e2fe3314cd4549
> Author: Howard Chu <hyc(a)symas.com>
> Date: Sat Jul 26 18:16:02 2014 -0700
>
> Fix MIPS cache coherency on Linux
>
> MIPS chips require manual control of on-chip caches. The cacheflush
> syscall being used here only exists on MIPS Linux, other OSs will
> require revisiting.
I may be guessing wrong what's going on here, but anyway:
CACHEFLUSH looks like it belongs before setting me_txns->mti_txnid
which tells other threads/processes to use the new metapage.
If so, MDB_NOLOCK may be in trouble since it uses pick_meta()
instead of mti_txnid. Should there be a separate CACHEFLUSH after
writing the datapages if MDB_NOLOCK, and the current CACHEFLUSH
should just flush the metapages?
Does the code contradict this comment above, or is it about
something else?
/* Memory ordering issues are irrelevant ... */
--
Hallvard
8 years, 10 months
