docs: recommend InnoDB over MEMORY engine for Boost tables - #217
Open
somethingwithproof wants to merge 2 commits into
Open
docs: recommend InnoDB over MEMORY engine for Boost tables#217somethingwithproof wants to merge 2 commits into
somethingwithproof wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR improves the Boost.md documentation to recommend InnoDB over the MEMORY storage engine for Cacti's Boost tables, addressing performance and reliability issues — especially on multi-process or multi-Data-Collector Cacti deployments as described in linked issue #106.
Changes:
- Added a
> **Recommendation**callout block in the Prerequisites section advising the use of InnoDB for Boost tables on most installations, with rationale around race conditions, MariaDB Galera, and MySQL replication incompatibilities. - Added a
> **Warning**callout block in the Flushing section reminding users that MEMORY tables are wiped on every DB restart. - Fixed three typos (
formally→formerly, duplicatethe the→the,Utilityes→Utilities) and fixed invalid two-tableALTER TABLESQL into two separate valid statements.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
somethingwithproof
force-pushed
the
fix/106-boost-innodb-recommendation
branch
from
March 10, 2026 20:57
78f2ae6 to
94a2865
Compare
Refs Cacti#106 Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
somethingwithproof
force-pushed
the
fix/106-boost-innodb-recommendation
branch
from
March 15, 2026 05:20
94a2865 to
ef81c66
Compare
poller_output_boost ships as InnoDB, not MEMORY. The prior wording claimed Cacti installs MEMORY tables by default and pointed readers to conversion steps that convert to MEMORY, contradicting the InnoDB recommendation. Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
Contributor
Author
|
Already fixed in the current content -- Boost.md now says InnoDB "is the recommended engine" rather than "default and recommended," matching the fact that several Boost tables still ship as MEMORY by default. No further changes needed; resolving. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
poller_output_boostships as InnoDB by defaultTest plan
Closes #106