Description of problem: In cn=monitor bytessent and possibly other values (like entriessent, opsinitiated, opscompleted) are overflowing at 2^32-1. Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-11.el7 How reproducible: always Steps to Reproduce: 1. Add 100k entries 2. Search for all entries 3. Check value of bytessent in cn=monitor 4. Repeat steps 2-3 Actual results: After some time bytessent passes 2^32-1 boundary and starts from 0 Expected results: Max value of bytessent is expected to be 2^64-1. Additional info: 389-ds-base-1.2.11 is not affected.
Regression was introduced in fc0036e2d35e189c2a34f4722fbebda548cf94b9
Metadata Update from @vashirov: - Issue set to the milestone: 1.3.4.11
Metadata Update from @mreynolds: - Custom field version adjusted to 1.3.5 - Issue close_status updated to: None
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Closing as a duplicate of #48989
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to new - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/2104
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)