-
Bug
-
Resolution: Unresolved
-
Minor
-
rhel-9.5
-
None
-
No
-
Low
-
ZStream
-
rhel-idm-ds
-
ssg_idm
-
0
-
False
-
False
-
-
None
-
None
-
Regression Exception
-
None
-
None
-
None
What were you trying to do that didn't work?
nsslapd-mdb-max-size accepts value in bytes. But it can't be any value, it should be a multiple of the page size, which can vary (4K, 16K, 64K on different architectures).
dscreate create-template lists the value as float and not as a multiple of the page size:
dscreate create-template | grep mdb_max_size # mdb_max_size (str) ;mdb_max_size = 15257305088.0
This was fixed in https://github.com/389ds/389-ds-base/commit/415eeadae62e9387f311d1a9c4808d590ea381b2 to support unit suffixes (Kb, Mb, Gb).
Setting the value using dsconf also accepts only bytes:
dsconf localhost backend config set --help
...
--mdb-max-size MDB_MAX_SIZE
Sets the lmdb database maximum size (in bytes).
And in the WebUI max size is specified in megabytes.
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
389-ds-base-2.5.2-2.el9_5.x86_64
How reproducible is this bug?:
always
Steps to reproduce
- See command above
Expected results
DS tools should be consistent and accept values with unit suffixes/
- is duplicated by
-
RHEL-119226 Units for changing MDB max size are not consistent across different tools
-
- Closed
-
- links to