We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
During a Re-Index, if a Data Source is disabled, Cacti's API is not purging it's records from the Boost table resulting in memory leakage and failed boost runs.
Steps to reproduce the behavior:
Create 10's of thousands of Data Sources from Data Queries
Have the re-index not fail, bur return only a fraction of the records.
Ensure your boost table has > 6M records
Attempt to do a boost run and watch the memory value. Boost can consume several GB of memory.
Boost should not leak memory, Cacti should remove these Data Sources from the Boost tables as well during the disable process.
The text was updated successfully, but these errors were encountered:
Fixing Issue #3477
Boost leaking memory when a large number of Data Sources disabled
Just one comment:
function boost_rrdtool_function_update have only two return_value '' or OK
So I prefer to ignore '' in boost_process_output, and do not output WARN for each disabled DataSource:
2020/04/21 05:17:45 - BOOST WARNING: RRD Update Warning '' for Local Data ID '97063'
Sorry, something went wrong.
No branches or pull requests