RE: mysqlcheck downtime > 30 minutes for Java web application

2014-06-12 Thread Martin Gainty
> From: tyfan...@uoregon.edu > To: webleh...@gmail.com; mysql@lists.mysql.com > Subject: RE: mysqlcheck downtime > 30 minutes for Java web application > Date: Fri, 13 Jun 2014 00:02:48 + > > I woul

RE: mysqlcheck downtime > 30 minutes for Java web application

2014-06-12 Thread Martin Gainty
> From: tyfan...@uoregon.edu > To: webleh...@gmail.com; mysql@lists.mysql.com > Subject: RE: mysqlcheck downtime > 30 minutes for

RE: mysqlcheck downtime > 30 minutes for Java web application

2014-06-12 Thread Tyfanie Wineriter
ecially for version 5.6? ~ Tyfanie Wineriter ~ Database Administrator University of Oregon 1212 University of Oregon Eugene, OR 97402-1212 (541) 346-1366 -Original Message- From: Lukas Lehner [mailto:webleh...@gmail.com] Sent: Wednesday, June 11, 2014 6:38 AM To: mysql Subject: mysqlcheck d

mysqlcheck downtime > 30 minutes for Java web application

2014-06-11 Thread Lukas Lehner
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. $ ti