Berkeley DB's mpool stat declares:
uintmax_t st_cache_hit; /* Pages found in the cache. */ uintmax_t st_cache_miss; /* Pages not found in the cache. */
which do not have 32 bit limit.
Internally dbcachetries is calculated as follows.
cache_tries = (mpstat->st_cache_miss + mpstat->st_cache_hit);
The type of cache_tries is currently u_int32_t, which should be adjusted to uintmax_t.
This is the result of the change. There is no more (2^32 - 1) limitation.
dn: cn=monitor,cn=ldbm database,cn=plugins,cn=config dbcachehits: 8060909425 dbcachetries: 8061909425 dbcachehitratio: 99
The same issue was fixed in Ticket #48899 - Values of dbcachetries/dbcachehits in cn=monitor could overflow.
Closing as dup.
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @vashirov: - Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1956
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Duplicate)
Login to comment on this ticket.