#47701 Make retro changelog trim interval programmable
Closed: wontfix None Opened 10 years ago by nhosoi.

Currently, retro changelog trim interval is hardcoded with 5 minutes.

define CHANGELOGDB_TRIM_INTERVAL 3001000 / 5 minutes

Better have a control on the interval based upon the DS usage -- e.g., if there is no updates, we don't need to call changelog_trim via retrocl_housekeeping every 5 minuges.


Description: Currently, retro changelog trim interval is hardcoded
with 5 minutes.
#define CHANGELOGDB_TRIM_INTERVAL 3001000 / 5 minutes

Better have a control on the interval based upon the DS usage --
e.g., if there is no updates, we don't need to call changelog_trim
via retrocl_housekeeping every 5 minutes.

Reviewed by Rich (Thank you!!)

Pushed to master:
98ddd81..bb4f0c4 master -> master
commit bb4f0c4

Additional push for fixing compiler errors:
681be0d..b377d7d master -> master
commit b377d7d

git patch file (master) -- Fixing "Coverity 12435 - Resource leak"
0001-Ticket-47701-Make-retro-changelog-trim-interval-prog.3.patch

Thank you for reviewing the change, Rich!

Pushed to master:
f7c5dc2..cd35419 master -> master
commit cd35419

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.3 - 2/14 (February)

7 years ago

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/1037

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata