May 24, 2012

Post: Troubleshooting MySQL Memory Usage

…_TIME: 2012-03-21 05:52:02 UPDATE_TIME: NULL *************************** 3. row *************************** SESSION_ID: 7231 TABLE_SCHEMA: test TABLE_NAME: z ENGINE: InnoDB…: 16384 INDEX_LENGTH: 0 CREATE_TIME: NULL UPDATE_TIME: NULL 3 rows in set (0.00 sec) Innodb Memory Usage Finally it is…) File system 294352 (82672 + 211680) Lock system 318875832 (318747272 + 128560) Recovery system 0 (0 + 0) Threads 425080 (406936 + 18144) Dictionary memory…

Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

…, LVM snapshot should be recoverable 100% of the time. You might have found recovery bug but there have been very few of… on the same partition or synchronization of binary log and innodb snapshot. In certain versions FLUSH TABLES WITH READ LOCK would…

Post: Improving InnoDB recovery time

Speed of InnoDB recovery is known and quite annoying problem. It was discussed many times, see: http://bugs.mysql.com/bug.php?id=29847 http://dammit.lt/2008/10/26/innodb-crash-recovery/ This is problem when your InnoDB crashes, it may takes long time to start. Also it…

Post: Innodb Recovery - Is large buffer pool always better ?

Innodb crash recovery on box with large amount of memory (64GB) with Innodb Buffer pool configured to be just a bit over 20GB. Innodb recovery was taking long hours with reasonably sized Innodb log files… pages in the flush list which takes a lot of timeInnodb is smart about a way it flushes pages, it tries…

Post: Magic Innodb Recovery self healing

innodb_force_recovery=4. So I decided to check if I’m to get lucky second time today. And Indeed Restarting Innodb with innodb_force_recovery…”. So when dealing with Innodb recovery for bad corruptions you may want to: – Start with lower innodb_force_recovery settings and see which one…

Post: How to estimate time it takes Innodb to Recover ?

… log file time may have recovery time of 5-10 minutes. To understand things affecting recovery time you better to understand how Innodb recovery works. When Innodb recovers from logs it finds the last checkpoint time. Innodb has fuzzy…

Post: MySQL Crash Recovery

… the problems. As I already wrote innodb_log_file_size and innodb_buffer_pool_size affect recovery time significantly as well as your workload. I should also mention if you have innodb_file_per_table=1 your recovery speed…

Post: Choosing proper innodb_log_file_size

… to Innodb tables decent size of innodb_log_file_size is important for MySQL Performance. However setting it too large will increase recovery time, so in case of MySQL crash or power failure it may take long time before MySQL Server… it to recover. Doing this several times you should be able to estimate how long recovery time take and adjust your logs apropriately…

Post: Recovery beyond data restore

… careful such as using sync-binlog innodb_flush_logs_at_trx_commit=1 and only using Innodb tables to be OK in… like Innodb corruption or soft crash which you can’t recover promptly enough. In this case most typically you would plan recovery… restore from several of backup generations and do point in time recovery. Timing recovery is also important. Especially for write intensive environments it may…

Post: Recovering Innodb table Corruption

… up to be empty after the run. At the same time I saw some data could be selected. The problem is… higher innodb_force_recovery modes to block purging activity, insert buffer merge or recovery from transactional logs all together. Though the lower recovery mode… work well – in this case you may wish to use Innodb Recovery Toolkit which is also helpful in cases you’ve want…