Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4349

The documentation of the behaviour of 'threads=auto' in containers is incorrect

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Trivial
    • Resolution: Fixed
    • 22.08
    • 22.08.2
    • Documentation
    • None

    Description

      The documentation claims that threads=auto would cause MaxScale, when running in a container, to use the CPU resources available in the container when deciding how many routing threads to use. That is incorrect, MaxScale will always base that decision on the number of cores available on the computer in which the container is running. That may lead MaxScale to use more resources than what is available in the container.

      Attachments

        Activity

          People

            johan.wikman Johan Wikman
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.