Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 5.5.31
    • 5.5.32
    • None
    • None
    • 2 Quad Intel Xeon 2,2 Ghz - 12 GB memory OS : CentOS 5.8

    Description

      I migrated from MySQL 5.1 to MariaDB 5.5.31 on many servers during three last months. On some servers, i see a big change i consumer memory which requires a stop-start of MariaDB to release memory. The size of data evolves very little. The attachments illustrate the change since the migration of one server made on 05/28/2013. Thank for your help.

      Attachments

        1. engine_memory_usage.txt
          1.0 kB
          SUJET
        2. engine_memory_usage.txt
          1.0 kB
          SUJET
        3. memory_usage (3 Months).PNG
          58 kB
          SUJET
        4. my.cnf
          2 kB
          SUJET
        5. screenshot-1.jpg
          125 kB
          SUJET
        6. show_global_status.txt
          26 kB
          SUJET
        7. show_variables.txt
          178 kB
          SUJET
        8. swap_usage (3 Months).PNG
          47 kB
          SUJET

        Issue Links

          Activity

            pendexgabo Gabriel Sosa added a comment -

            how is turning off the query cache a solution here? Sounds like removing an totally relevant part of the performance component of the server...

            pendexgabo Gabriel Sosa added a comment - how is turning off the query cache a solution here? Sounds like removing an totally relevant part of the performance component of the server...

            It's not a solution, it's a workaround till the next release (5.5.32) where the bug is supposed to be fixed.

            elenst Elena Stepanova added a comment - It's not a solution, it's a workaround till the next release (5.5.32) where the bug is supposed to be fixed.
            pendexgabo Gabriel Sosa added a comment -

            Looks like you guys just release the version 5.5.32 and this fix is not on it. Do you have any certain release date for this bugifx? Also would you help guys if we provide us some more info on this matter ?

            thanks

            pendexgabo Gabriel Sosa added a comment - Looks like you guys just release the version 5.5.32 and this fix is not on it. Do you have any certain release date for this bugifx? Also would you help guys if we provide us some more info on this matter ? thanks
            elenst Elena Stepanova added a comment - - edited

            The fix should be in 5.5.32 release. The bug was fixed in XtraDB 5.5.32 (at least it is marked as such in https://bugs.launchpad.net/percona-server/+bug/1170103), and MariaDB 5.5.32 includes XtraDB 5.5.32.

            We didn't have a reproducible test case to verify it, so please re-open the issue (or comment on it to get it re-opened) if you still have the problem with MariaDB 5.5.32,

            elenst Elena Stepanova added a comment - - edited The fix should be in 5.5.32 release. The bug was fixed in XtraDB 5.5.32 (at least it is marked as such in https://bugs.launchpad.net/percona-server/+bug/1170103 ), and MariaDB 5.5.32 includes XtraDB 5.5.32. We didn't have a reproducible test case to verify it, so please re-open the issue (or comment on it to get it re-opened) if you still have the problem with MariaDB 5.5.32,
            pendexgabo Gabriel Sosa added a comment -

            excellent! perfect. Thanks for your time

            pendexgabo Gabriel Sosa added a comment - excellent! perfect. Thanks for your time

            People

              Unassigned Unassigned
              psujet SUJET
              Votes:
              2 Vote for this issue
              Watchers:
              9 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.