https://bugs.openldap.org/show_bug.cgi?id=9222
Bug ID: 9222
Summary: Fix presence list to use a btree instead of an AVL
tree
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
[23:34] <…
[View More]hyc> ok, so far heap profile shows that memory use during refresh is
normal
[23:35] <hyc> not wonderful, but normal. mem usage grows because we're
recording the present list while receiving entries in the refresh
[23:36] <hyc> I'm seeing for 1.2GB of data about 235MB of presentlist
[23:36] <hyc> which is pretty awful, considering presentlist is just a list of
UUIDs
[23:36] <hyc> being stored in an avl tree
[23:37] <hyc> a btree would have been better here, and we could just use an
unsorted segmented array
[23:42] <hyc> for the accumulation phase anyway. we need to be able to lookup
records during the delete pphase
[00:05] <hyc> this stuff seriously needs a rewrite
[01:13] <hyc> 2.8M records x 16 bytes per uuid so this should be no more than
48MB of overhead
[01:13] <hyc> and instead it's 3-400MB
--
You are receiving this mail because:
You are on the CC list for the bug.
[View Less]
https://bugs.openldap.org/show_bug.cgi?id=9379
Issue ID: 9379
Summary: slapd should reject invalid listener URLs
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: trivial
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Most common instance of invalid listener URLs …
[View More]is specifying an ldapi URL
without URLencoding the socket pathname. Then the slashes in the pathname are
treated as URL field separators, which yields a pathname quite different from
what was intended.
--
You are receiving this mail because:
You are on the CC list for the issue.
[View Less]
https://bugs.openldap.org/show_bug.cgi?id=9372
Issue ID: 9372
Summary: Use POSIX semaphores by default on MacOS
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: kriszyp(a)gmail.com
Target Milestone: ---
Created attachment 775
--> https://bugs.…
[View More]openldap.org/attachment.cgi?id=775&action=edit
Set POSIX semaphore as default for MacOS
On Apple/MacOS, System V semaphores have a limit of 10 open robust (SEM_UNDO)
semaphores at once per process, which can cause problems if a process has many
open database environments/transactions open at once. Using POSIX semaphores
eliminates this problems and supposedly have a little bit better performance.
The attached patch (also at
https://github.com/kriszyp/lmdb/commit/0971512f6a4aa5b05f99e481a6687d4802f7…)
sets that as the default, and reverts back to System V semaphores with
MDB_USE_ROBUST, since MacOS does not support robust POSIX locking.
--
You are receiving this mail because:
You are on the CC list for the issue.
[View Less]
https://bugs.openldap.org/show_bug.cgi?id=9364
Issue ID: 9364
Summary: Rework encryption API
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Currently a single initialization vector is set at env creation …
[View More]time, and is
used for the entire life of the DB. Ideally it should be a value uniquely
generated on every write to a page. The most straightforward approach would be
to use a combination of the page number and txid. Even better would be to use a
keyed hash of these two values.
--
You are receiving this mail because:
You are on the CC list for the issue.
[View Less]
https://bugs.openldap.org/show_bug.cgi?id=9377
Issue ID: 9377
Summary: Golang built-in race-detector tooling catching pointer
arithmetic error on Win
Product: LMDB
Version: 0.9.25
Hardware: x86_64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: AskAlexSharov(a)gmail.com
…
[View More]Target Milestone: ---
Detector of race-conditions which built into Golang tooling shows next error on
Windows x86_64:
mdb.c:1487:7:
char buf[MSGSIZE+PADSIZE], *ptr = buf;
^
fatal error: checkptr: pointer arithmetic computed bad pointer value
Link to CI where error is reproducible:
https://github.com/ledgerwatch/lmdb-go/pull/8/checks?check_run_id=131269917…
--
You are receiving this mail because:
You are on the CC list for the issue.
[View Less]
https://bugs.openldap.org/show_bug.cgi?id=9360
Issue ID: 9360
Summary: MDB_BAD_TXN: Transaction must abort, has a child, or
is invalid
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: spam(a)markandruth.co.uk
Target Milestone: --…
[View More]-
I have 2 python scripts writing to a database (lmdb 0.9.26, py-lmdb 0.98) and
5-10 lua processes (with lightningmdb module which uses lmdb 0.9.22) which are
long-running serving queries from the database.
The database seems fine, not corrupted, and the python writes still working all
the time. But periodically (perhaps 10-20% of the time), in a way I am unable
to reliably reproduce, when the lua starts up every time a query is issued txn
dbi_open returns "MDB_BAD_TXN: Transaction must abort, has a child, or is
invalid". A direct restart of the processes does not fix this issue, however
stopping lua+python and then starting again after a 5-20s wait usually fixes
the issue. This has been reproduced over multiple servers but I'm at a loss as
to how to debug this any further?
--
You are receiving this mail because:
You are on the CC list for the issue.
[View Less]
https://bugs.openldap.org/show_bug.cgi?id=9370
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Group|OpenLDAP-devs |
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.