Skip to content

Update documentation - Boost table engine for large Cacti installations #106

Description

@browniebraun

It should be recommended for large Cacti installations not to stay with Boost tables using the MEMORY engine, especially in combination with the multiprocessing update feature 1.2.17 will provide.

My prod installation was totally in trouble yesterday caused by a race condition between the different processes waiting for memory table locks. If you have a fast storage system the recommendation should always be to use only INNODB engine for all Boost tables.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions