You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TheWitness opened this issue
Apr 19, 2020
· 2 comments
Labels
blockerBlocking releaseboostBoost related issuebugUndesired behaviourconfirmedBug is confirm by dev teamperformancePerformance related affects big sitesresolvedA fixed issue
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.
To Reproduce
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.
Expected behavior
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:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
blockerBlocking releaseboostBoost related issuebugUndesired behaviourconfirmedBug is confirm by dev teamperformancePerformance related affects big sitesresolvedA fixed issue
Describe the bug
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.
To Reproduce
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.
Expected behavior
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: