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

Got error 2 "No such file or directory" when querying TokuDB_fractal_tree_info

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.17, 5.5(EOL), 10.0(EOL)
    • 5.5.44, 10.0.20
    • None
    • CentOS release 6.6 (Final)
      Kernel: 2.6.32-358.23.2.el6.x86_64
    • 5.5.45

    Description

      We were running a very large insert (500M rows) from an innodb table to a tokudb table.
      The insert failed and the mariadb crashed. Which came 1st is still unknown at this point.

      The tokudb table has 700 partitions with 4 indexes.

      After the failures anything regarding TokuDB metadata was returning that error: No such file or directory. Whether we were looking at this table or another.
      show table status...
      Select * from TokuDB_fractal_tree_info;

      Using sysdig, we found out that no mater what table you would be looking at, tokudb opens all tokudb related files. And in this case, the file it was looking for, existed but had a different name.
      The file it was looking for was:
      /data/mysql/tokudb_data/_MYDB_MYTAB_P_day_20140101_key_idx1_9a60c_2_1b_B_3.tokudb
      But the file was named:
      /data/mysql/tokudb_data/_MYDB_MYTAB_P_day_20140101_key_idx1_99906_5_1b.tokudb

      We shutdown the database, and renamed the file, and all worked after that.

      We tried many thing to get around the problem, one was to drop the table, which wasn't possible as it was giving us the same error.

      Attachments

        Issue Links

          Activity

            ynaguib Younes Naguib added a comment -

            I sent you all the info by email.
            Anything special you would like me to monitor or log to make sure we have a full view if this happens again?

            y

            ynaguib Younes Naguib added a comment - I sent you all the info by email. Anything special you would like me to monitor or log to make sure we have a full view if this happens again? y
            prohaska7 Rich Prohaska added a comment -

            Hello. Need the tokudb recovery log files (log*.tokulog*).

            prohaska7 Rich Prohaska added a comment - Hello. Need the tokudb recovery log files (log*.tokulog*).
            ynaguib Younes Naguib added a comment -

            I followed you advise and created a table with the same structure, renamed the files to reflect the files in the dictionary, then dropped the old table again.
            It worked nicely.
            As for reproducing the bug, I will see what I can do.

            Thanks for your help.

            ynaguib Younes Naguib added a comment - I followed you advise and created a table with the same structure, renamed the files to reflect the files in the dictionary, then dropped the old table again. It worked nicely. As for reproducing the bug, I will see what I can do. Thanks for your help.
            prohaska7 Rich Prohaska added a comment -

            The original bug of getting an error when querying the tokudb_fractal_tree_info table is fixed in tokudb 7.5.7. See https://tokutek.atlassian.net/browse/DB-829.

            prohaska7 Rich Prohaska added a comment - The original bug of getting an error when querying the tokudb_fractal_tree_info table is fixed in tokudb 7.5.7. See https://tokutek.atlassian.net/browse/DB-829 .

            Thanks.
            We still have 7.5.6 in our 5.5 and 10.0 trees, so it should be fixed with the next merge.

            elenst Elena Stepanova added a comment - Thanks. We still have 7.5.6 in our 5.5 and 10.0 trees, so it should be fixed with the next merge.

            People

              serg Sergei Golubchik
              ynaguib Younes Naguib
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.