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

MaxCtrl is limited to 2GB of memory

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.19
    • Fix Version/s: 2.5.21, 6.3.1
    • Component/s: maxctrl
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-157

      Description

      If MaxScale is configured to use a lot of memory for the query classifier cache, calling the show qc_cache endpoint can cause MaxCtrl to run out of memory even if enough memory would be available to it. This happens because NodeJS by default limits memory and the value of max_old_space_size needs to be increased.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            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.