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

TokuDB fails to load, even when following instructions on website

Details

    Description

      I have disabled transparent hugepages, yet when I run
      install soname 'ha_tokudb';
      I get 

      ERROR 1123 (HY000): Can't initialize function 'TokuDB'; Plugin initialization function failed.

      This issue broke my website when I upgraded from Ubuntu 13.10 with MariaDB 5.5.34 to Ubuntu 14.04 with MariaDB 10.0.10. Did I miss anything? Is there another cause for this issue?

      Attachments

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-6173 TokuDB cannot start after upgrade if the previous version was not shut down in a clean way

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

          Activity

            Ascending order - Click to sort in descending order
            View 19 older comments
            ascom Andrew Sun (Inactive) added a comment -

            Okay, the server actually does not fail to start when the config option is set. Yay.

            However, TokuDB still fails to load, with the could not upgrade version 24 database error. I will try to swap out the .so again.

            ascom Andrew Sun (Inactive) added a comment - Okay, the server actually does not fail to start when the config option is set. Yay. However, TokuDB still fails to load, with the could not upgrade version 24 database error. I will try to swap out the .so again.
            ascom Andrew Sun (Inactive) added a comment -

            I have 5.5.37 installed, and when using the ha_tokudb.so from 5.5.36, I get the same not supported errors.

            ascom Andrew Sun (Inactive) added a comment - I have 5.5.37 installed, and when using the ha_tokudb.so from 5.5.36, I get the same not supported errors.
            ascom Andrew Sun (Inactive) added a comment - - edited

            I fixed it!

            I installed 5.5.36 from the Ubuntu repos, and then copied the tokudb library from the 5.5.36 deb I downloaded from the "official" source. Now I can upgrade!

            Thanks for your patience in helping me resolve this issue.

            ascom Andrew Sun (Inactive) added a comment - - edited I fixed it! I installed 5.5.36 from the Ubuntu repos, and then copied the tokudb library from the 5.5.36 deb I downloaded from the "official" source. Now I can upgrade! Thanks for your patience in helping me resolve this issue.
            elenst Elena Stepanova added a comment - - edited

            Great!
            My apologies for the unpleasant experience. I hope eventually we will be able to get TokuDB be more friendly in terms of upgrade.

            elenst Elena Stepanova added a comment - - edited Great! My apologies for the unpleasant experience. I hope eventually we will be able to get TokuDB be more friendly in terms of upgrade.
            elenst Elena Stepanova added a comment -

            I have created an explicit request MDEV-6173 for improving the upgrade logic, and MDEV-6174 for documenting the current situation. Technically MDEV-6173 is a duplicate of MDEV-6165, but I wanted to make a point that it's a general problem, not a user error as it might seem from the current issue. If it gets fixed in TokuDB, or if we find some other way to minimize the risk, this issue will be closed along with MDEV-6173. Meanwhile, I will keep it open.

            elenst Elena Stepanova added a comment - I have created an explicit request MDEV-6173 for improving the upgrade logic, and MDEV-6174 for documenting the current situation. Technically MDEV-6173 is a duplicate of MDEV-6165 , but I wanted to make a point that it's a general problem, not a user error as it might seem from the current issue. If it gets fixed in TokuDB, or if we find some other way to minimize the risk, this issue will be closed along with MDEV-6173 . Meanwhile, I will keep it open.

            People

              serg Sergei Golubchik
              ascom Andrew Sun (Inactive)
              Votes:
              0 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.