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

Kafkacdc and avrorouter leak memory if all tables are non-transactional

    XMLWordPrintable

Details

    • Can result in unexpected behaviour
    • The kafkacdc and avrorouter modules allocated an unbounded amount of memory if all tables were non-transactional.

    Description

      The fix to MXS-6671 handled only the case where transactional tables commit transactions where it uses the XID event as a marker where the table maps can be dropped. MariaDB itself uses a flag in the row event and MaxScale should do the same as otherwise non-transactional tables never free the table maps.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MXS-6671 Maxscale memory is increasing linearly over the period of a week

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.5d
                  0.5d

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.