-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After enabling TokuDB got error failed to execute: SELECT CONCAT(CONCAT(TABLE_SCHEMA, '.'), TABLE_NAME),DATA_FREE #316
Comments
This is a fun bug :) can you give me more details ? |
Mariadb version 10.1.22 running on Debian Jessie. The same was with 10.0.* (last) version. It has begun after converting one database to TokuDB. select * from information_schema.TABLES; |
I tried to debug the issue myself. If I run +-----------------------------------------------+----------------------+ The piwik.* tables are the ones I've converted from InnoDB to TokuDB. We have highloaded piwik (visitor analytics platform) instance. |
Hi I have explore tokutek information and tokuDb is not very active since around 3 years. Have a look at : https://github.com/percona/tokudb-engine I think rely on tokudb engine is not the most clear and evident solution. I don't know what Mt can do for this issue if no more bug fix are performed on this engine. I propose to close this issue because I honestly do know what to do to fix that. |
Hi @iprok Can we close this issue as long as we can rely on Tokudb status information ? |
Hello, @jmrenouard ! Yes, sure. TokuDB is dead. |
Hi @iprok In my opinion, we can close this ticket. Do you share this idea ? |
I just ran into this same issue on the latest 1.7.20 version of mysqltuner, with MySQL 5.7 release. It seems there was never any change made to at exclude TokuDB and get past this error. I realize that it's been abandoned, but for large databases it can take a long time to get migrated over to another engine. Can we at least get a query that obeys order of operations? And, maybe an optional argument to "exclude" TokuDB from checks? Both of these queries fail, the first one being the one mysqltuner is using in 1.7.20. SELECT CONCAT(CONCAT(TABLE_SCHEMA, '.'), TABLE_NAME),DATA_FREE FROM information_schema.TABLES WHERE TABLE_SCHEMA NOT IN ('information_schema','performance_schema', 'mysql') AND DATA_LENGTH/1024/1024>100 AND DATA_FREE*100/(DATA_LENGTH+INDEX_LENGTH+DATA_FREE) > 10 AND NOT ENGINE='MEMORY' SELECT CONCAT(CONCAT(TABLE_SCHEMA, '.'), TABLE_NAME),DATA_FREE FROM information_schema.TABLES WHERE TABLE_SCHEMA NOT IN ('information_schema','performance_schema', 'mysql') AND DATA_LENGTH/1024/1024>100 AND DATA_FREE*100/(DATA_LENGTH+INDEX_LENGTH+DATA_FREE) > 10 AND NOT ENGINE='MEMORY' AND NOT ENGINE=‘TokuDB’ This query works, because it does proper order of operations and excludes the tables before doing math calculations. SELECT CONCAT(CONCAT(TABLE_SCHEMA, '.'), TABLE_NAME),DATA_FREE FROM information_schema.TABLES WHERE TABLE_SCHEMA NOT IN ('information_schema','performance_schema', 'mysql') AND NOT ENGINE='MEMORY' AND NOT ENGINE='TokuDB' AND DATA_LENGTH/1024/1024>100 AND DATA_FREE*100/(DATA_LENGTH+INDEX_LENGTH+DATA_FREE) > 10; |
Hello!
I've converted some of my tables to TokuDB from InnoDB and mysqltunner gives me the following error now:
[!!] failed to execute: SELECT CONCAT(CONCAT(TABLE_SCHEMA, '.'), TABLE_NAME),DATA_FREE FROM information_schema.TABLES WHERE TABLE_SCHEMA NOT IN ('information_schema','performance_schema', 'mysql') AND DATA_LENGTH/1024/1024>100 AND DATA_FREE*100/(DATA_LENGTH+INDEX_LENGTH+DATA_FREE) > 10 AND NOT ENGINE='MEMORY'
[!!] FAIL Execute SQL / return code: 256
If I run the query manually I get:
ERROR 1690 (22003): BIGINT UNSIGNED value is out of range in '(
information_schema
.TABLES
.DATA_FREE
* 100)'The text was updated successfully, but these errors were encountered: