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

MaxScale Global Memory Use Indicator

    XMLWordPrintable

    Details

    • Sprint:
      MXS-SPRINT-159, MXS-SPRINT-160, MXS-SPRINT-161, MXS-SPRINT-166, MXS-SPRINT-167

      Description

      Some of our customers are frustrated by the inability to monitor global memory usage from MaxScale using any internal reporting such as status variables.

      Occasionally MaxScale uses a larger than expected amount of memory, be it because large transactions are in-flight or because the history of commands gets unexpectedly large, for example, or due to memory leaks in a current version of a MaxScale service or supporting tool such as SQLite.

      The desire is to have a global variable in MaxScale reporting on the current cumulative memory use off all MaxScale services, including the SQLite footprint, so that automated monitoring could become aware of potential problem situations and address them proactively.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              johan.wikman Johan Wikman
              Reporter:
              juan.vera Juan
              Votes:
              2 Vote for this issue
              Watchers:
              5 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.