Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.0.20
-
Fix Version/s: None
-
Component/s: Storage Engine - TokuDB
-
Environment:ubuntu 15.04 64 bit
Description
Sometimes TokuDB tables get corrupted, the server crash and will not start anymore. The only way I found to have the server running, is to delete all the .tokudb, .frm and .par files related to the table that caused the crash. The problem is that the information_schema.TokuDB_file_map table still shows the records related to the table, and any subsequent attempt to recreate the table produces the error: 17 "File exists". As reported in MDEV-7841, I "created a table with the same structure (and partitions), renamed the files to reflect the files in the dictionary, then dropped the old table again". Files are deleted from disk, but the information_schema.TokuDB_file_map table still shows the records. So I can't recreate the table with the same name. Please, can you suggest me a workaround to the problem? Is there a way to synchronize the file map with the real situation of existing files?
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Back to the question, I can report it to TokuDB on your behalf, but they will probably request more information from you, will you be ready to provide it?
Hello, sorry for the delay...
Yes, I will be ready from the next week because now I'm on holiday 
Thank you!
Hello, I'm ready to provide all the information needed.
Thank you.
----Messaggio originale----
Da: Elena Stepanova (JIRA) jira@mariadb.atlassian.net
Inviato: lunedì 24 agosto 2015 23:20
A: Risato Stefano (IR SCR)
Oggetto: [JIRA] (MDEV-8541) TokuDB file map table doesn't reflect the real situation of the files on the disk
Elena Stepanova commented on MDEV-8541:
---------------------------------------
Back to the question, I can report it to TokuDB on your behalf, but they will probably request more information from you, will you be ready to provide it?
–
This message was sent by Atlassian JIRA
(v7.0.0-OD-02-247#70102)
I have refiled it as https://tokutek.atlassian.net/browse/DB-872, so you can track it there. But I suppose for efficient communication you will need to have an account in TokuDB JIRA.
Sadly, the upstream report does not show any activity... We will still have to wait for Percona to work on it, I don't think we have manpower now to start digging deep into TokuDB.
Thank you. I started with a fresh install with version 10.1.7, and recreated the databases (about 300GB of compresseded TokuDB files) and in two weeks I did't have any problem. I hope for the future...
Bye
----Messaggio originale----
Da: Elena Stepanova (JIRA) jira@mariadb.atlassian.net
Inviato: lunedì 28 settembre 2015 23:41
A: Risato Stefano (IR SCR)
Oggetto: [JIRA] (MDEV-8541) TokuDB file map table doesn't reflect the real situation of the files on the disk
Elena Stepanova updated MDEV-8541:
----------------------------------
Labels: tokudb upstream (was: need_feedback tokudb upstream)
Sadly, the upstream report does not show any activity... We will still have to wait for Percona to work on it, I don't think we have manpower now to start digging deep into TokuDB.
–
This message was sent by Atlassian JIRA
(v7.0.0-OD-07-011#70107)
Risato Stefano,
We don't have direct connection to TokuDB gurus from our JIRA anymore, so we need to re-report TokuDB issues (non-specific to MariaDB) to their JIRA: https://tokutek.atlassian.net .
I can do it on behalf, but I thought you might want to do it yourself as it will be easier for you to track and follow.