Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10503

TokuDB logical row counts could get totally out of sync

Details

    Description

      Hi,

      FYI, the latest TokuDB version included in MariaDB 10.1.16 contains a nasty bug which could lead to cardinality wrongly set to 0 for all the keys (with the impact on the execution plan you can imagine).
      Detail of the bug (now fixed) upstream is here :

      https://tokutek.atlassian.net/browse/DB-1006

      Since it could lead to really bad issues, I wonder if you want to cherry pick the bugfix to include it in MariaDB, or just wait for the next TokuDB engine 5.6.32-77.1 release.

      Thanks,
      Jocelyn

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          philsweeney Phil Sweeney added a comment -

          serg FYI (I ran into this bug with 10.1.16 as well). I see you've just done the TokuDB merge but this fix isn't yet released by Percona so hasn't made it in.

          philsweeney Phil Sweeney added a comment - serg FYI (I ran into this bug with 10.1.16 as well). I see you've just done the TokuDB merge but this fix isn't yet released by Percona so hasn't made it in.
          Roze Reinis Rozitis added a comment -

          This seems to be fixed in the upstream now.
          Would be very nice to be included asap as the result of such behaviour in some cases brings down the DB in no-time.

          Roze Reinis Rozitis added a comment - This seems to be fixed in the upstream now. Would be very nice to be included asap as the result of such behaviour in some cases brings down the DB in no-time.
          joce jocelyn fournier added a comment -

          Too bad MariaDB 10.0.27 has just been release with TokuDB 5.6.31-77.0 instead of 5.6.32-78.0 which contain the fix for this bug.
          Do you plan to include 5.6.32-78.0 for the next MariaDB 10.1 release ?

          joce jocelyn fournier added a comment - Too bad MariaDB 10.0.27 has just been release with TokuDB 5.6.31-77.0 instead of 5.6.32-78.0 which contain the fix for this bug. Do you plan to include 5.6.32-78.0 for the next MariaDB 10.1 release ?
          serg Sergei Golubchik added a comment -

          Not for 10.1.17, but probably yes for 10.1.18

          serg Sergei Golubchik added a comment - Not for 10.1.17, but probably yes for 10.1.18
          joce jocelyn fournier added a comment -

          Then I will have to manually compile it to avoid having this issue for another month, it sucks
          Hopefully 10.1.18 will be shipped with MDEV-7258 fix at the same time...

          joce jocelyn fournier added a comment - Then I will have to manually compile it to avoid having this issue for another month, it sucks Hopefully 10.1.18 will be shipped with MDEV-7258 fix at the same time...
          joce jocelyn fournier added a comment - - edited

          This one seems to be fixed now

          joce jocelyn fournier added a comment - - edited This one seems to be fixed now
          elenst Elena Stepanova added a comment - - edited

          joce,

          Thanks for update.
          Closing as fixed in 10.0.28 and 10.1.18, because these are the last versions when TokuDB merge happened (5.6.33-79.0 and 5.6.32-78.1).

          elenst Elena Stepanova added a comment - - edited joce , Thanks for update. Closing as fixed in 10.0.28 and 10.1.18, because these are the last versions when TokuDB merge happened (5.6.33-79.0 and 5.6.32-78.1).

          People

            Unassigned Unassigned
            joce jocelyn fournier
            Votes:
            1 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.