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

infinite memory usage, possible leak

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.5
    • Fix Version/s: 2.3.7
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-80

      Description

      Under 2.3.5 the memory usage keeps increasing over time, until the machine finally goes OOM.
      I did manage to make a core dump of the process but running under valgrind for a long time isn't something I managed to do.

      The config is as follows

      [Read-Write-Service]
      type=service
      router=readwritesplit
      servers=db1,db2,db3
      user=maxscale
      password=XXX
      connection_keepalive=30
      #max_sescmd_history=50
      disable_sescmd_history=true
      master_accept_reads=false
      master_failure_mode=fail_on_write
      enable_root_user=true
      #master_reconnection=true
      #prune_sescmd_history=true
      #session_track_trx_state=true
      causal_reads=true
      causal_reads_timeout=2
      

      as you can see I already disabled sescmd history to rule this out. The core dump is quite large and I cannot upload it publicly as I'm not sure it doesn't contain any sensitive data but if there is anything I can do with it to help out please let me know.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              dicode Tim Westervoorde
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration