Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. 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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.4.12
    • Fix Version/s: 22.08.0
    • Component/s: Core
    • Labels:
      None

      Description

      A container with 512MB Starts with 60GB qcc because the host has 380GB.

      static int64_t DEFAULT_QC_CACHE_SIZE = get_total_memory() * 0.15;

      It seems possible to determine from inside if a process it's running inside a container.
      Not sure if it's possible to get the allowed resources for auto sizing.

      In this case auto sizing is dangerous and can lead to memory problems.

      Ideally MaxScale should either demand explicit settings for the autosized ones, warn or refuse to start.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              claudio.nanni Claudio Nanni
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.