New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make retro changelog trim interval programmable #1037
Comments
Comment from nhosoi (@nhosoi) at 2014-02-18 03:54:10 Description: Currently, retro changelog trim interval is hardcoded Better have a control on the interval based upon the DS usage -- |
Comment from nhosoi (@nhosoi) at 2014-02-18 03:58:47 git patch file (master) |
Comment from nhosoi (@nhosoi) at 2014-02-19 03:36:52 git patch file (master) -- fixing syntax errors |
Comment from nhosoi (@nhosoi) at 2014-02-24 23:52:34 git patch file (master) -- Fixing "Coverity 12435 - Resource leak" |
Comment from rmeggins (@richm) at 2014-02-25 00:06:25 ack |
Comment from nhosoi (@nhosoi) at 2017-02-11 22:58:02 Metadata Update from @nhosoi:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47701
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.
The text was updated successfully, but these errors were encountered: