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

MaxScale needs to detect it is running in a container

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • None
    • 22.08.0
    • Core
    • None

    Description

      At startup, MaxScale detects how many CPU cores and memory the system has and acts accordingly; e.g. starts as many routing threads as there are cores and uses at most 15% of the memory for the query classifier cache.

      However, if MaxScale runs in a Docker container whose number of CPU cores and amount of memory has been restricted and is less than what the host system has, the detection does not work correctly as the numbers reported by the OS in the container are those of the host system and not what is available in the container.

      Thus, in a restricted container MaxScale may attempt to use more resources than what is available, which may lead to performance and other issues.

      MaxScale should detect when it is running in a container and adapt to the resources available in the container.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MXS-4176 thread=auto does work well on docker or kubernetes circumstance

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MXS-4368 Detect if maxscale is running inside a container and either warn about it or refuse to start to avoid memory and threads overallocation

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MXS-3269 Make it possible to change at runtime the number of threads used by MaxScale

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MXS-4179 Verify that cgroup detection works

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MXS-5122 Scale everything according to the amount of available container resources

          • Major - Major loss of function.
          • Closed

          Activity

            People

              markus makela markus makela
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.