Lukas Lehner mysqlcheck downtime > 30 minutes for Java web application
Jun 11, 2014; 15:38
Lukas Lehner
mysqlcheck downtime > 30 minutes for Java web application
Hi
I read in "MySQL, Fifth Edition" by Paul DuBois that we should do a regular mysqlcheck.
We have all InnoDB tables. As far as I unterstand the tables get read and write locked during mysqlcheck.
The database will grow 100x in size, at the moment only initial load.
It means big downtime.
$ time mysqlcheck --all-databases [...]
real 29m41.449s user 0m0.019s sys 0m0.015s
mysql> SELECT table_schema "Data Base Name", SUM( data_length + index_length) / 1024 / 1024 -> "Data Base Size in MB" FROM information_schema.TABLES GROUP BY table_schema ; +--------------------+----------------------+ | Data Base Name | Data Base Size in MB | +--------------------+----------------------+ | imzweffefr | 38420.97170544 | | information_schema | 0.00781250 | | mysql | 0.63046169 | +--------------------+----------------------+ 3 rows in set (5.86 sec)
You all do mysqlcheck? Is it really mandatory? What's the risk if I don't do it regularly?
Jun 13
Tyfanie Wineriter RE: mysqlcheck downtime > 30 minutes for Java web application
Jun 13, 2014; 00:02
Tyfanie Wineriter
RE: mysqlcheck downtime > 30 minutes for Java web application
Jun 12
Martin Gainty RE: mysqlcheck downtime > 30 minutes for Java web application
Jun 12, 2014; 22:05
Martin Gainty
RE: mysqlcheck downtime > 30 minutes for Java web application
Jun 12
Martin Gainty RE: mysqlcheck downtime > 30 minutes for Java web application
Jun 12, 2014; 22:07
Martin Gainty
RE: mysqlcheck downtime > 30 minutes for Java web application
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!